Repository navigation
chore: remove temporary min-release-age exclusion - #103
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposal:
min-release-ageexclusion forfast-json-stringifyfrom.npmrc.Problem:
#102 added the exclusion because
fast-json-stringify@7.3.0, required by theobjectMechanismtests, had just been published and was younger than the 7 days ofmin-release-age. 7.3.0 was published on 2026-11-05 at 10:27 UTC, so since 2026-11-12 at 10:27 UTC it satisfies the rule on its own and the exclusion is no longer needed.Change:
.npmrc: two lines removed, the comment andmin-release-age-exclude[]=fast-json-stringify.Tests:
With the exclusion removed,
npm install(npm 11) resolvesfast-json-stringify@7.3.0, and lint, the unit tests and the type tests pass.Note: