Repository navigation
chore: exempt @profullstack/* from minimumReleaseAge - #320
Merged
Merged
Conversation
Our own packages; version-pinned excludes made every fleet bump wait 24h. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Version-pinned
minimumReleaseAgeExcludeentries for our own packages meant every new release of them failed CI for 24h (ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION). Replace them with one'@profullstack/*'rule; third-party packages keep the 1-day gate.🤖 Generated with Claude Code