chore: re-pin release-age excludes to exact versions - #66
Merged
Conversation
The bare-name entries were a workaround for a failure on an older vp-managed pnpm engine; the current engine honors pkg@version form (verified both in fresh resolution and the frozen-lockfile verifier). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the workspace’s supply-chain policy configuration to pin minimumReleaseAgeExclude entries to explicit pkg@version strings, aligning the config with the current behavior of the verifier (and avoiding the prior bare-name workaround).
Changes:
- Replace bare package names in
minimumReleaseAgeExcludewith exact version pins for Effect packages and@uinaf/skillcheck. - Update the inline comment to reflect the current accepted constraint format (exact versions or
||unions; no ranges).
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
|
🎉 This PR is included in version 2.4.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Part of the repo modernization program adjacent-findings backlog (item: Vite+ exclude investigation).
The bare-name
minimumReleaseAgeExcludeentries were a workaround recorded in #60 for a real failure on that day's vp-managed pnpm engine. The engine has rolled forward and now honorspkg@versionform in both fresh resolution and the frozen-lockfile verifier (verified with positive and negative controls). Re-pins all five entries to exact versions and replaces the stale comment with the actual constraint (exact or||unions only; ranges rejected by design).Verify green locally (pre-push hook ran the full chain).