Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: expose caches via the versions field #132

Merged
merged 1 commit into from
Mar 9, 2020
Merged

Conversation

TobiTenno
Copy link
Member

What did you fix? (provide a description or issue closes statement)

added a 'versions' field to expose the exports hashes

Considerations

  • Does this contain a new dependency? No
  • Does this introduce opinionated data formatting or manual data entry? No
  • Does this pr include the updated data files in a separate commit that can be reverted for a clean code-only pr? No
  • Have I run the linter through npm run lint? Yes
  • Is is a bug fix, feature request, or enhancement? Feature

@TobiTenno TobiTenno added Scope: Data How data is represented or cleaned up Type: Feature Request Severity3: Minor The defect affects minor functionality or non-critical data. It has an easy workaround. labels Mar 6, 2020
@TobiTenno TobiTenno requested a review from Kaptard March 6, 2020 20:55
@TobiTenno TobiTenno self-assigned this Mar 6, 2020
@TobiTenno TobiTenno merged commit 9bd3301 into development Mar 9, 2020
@TobiTenno TobiTenno deleted the expose-hashes branch March 9, 2020 12:49
@nexus-ci
Copy link
Contributor

🎉 This PR is included in version 1.856.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Scope: Data How data is represented or cleaned up Severity3: Minor The defect affects minor functionality or non-critical data. It has an easy workaround. Type: Feature Request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants