Repository navigation
fix(ci): validate generated version PRs without fresh changesets - #33
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.
Fix the release-candidate CI loop
PR #32 correctly consumes its changesets, but the generic contributor gate rejects the resulting version-only diff. Keep ordinary contributor Changesets validation, and accept consumed-changeset candidates only when they exactly reproduce versioning from their comparison base.
Verification
81/81 dependency-free script regressions passed independently, including 34 gate tests; syntax, YAML ordering and base/blob checks passed. Actual installed Changesets replay was not run locally (the process test uses a fake CLI). Exact-head full CI, then real replay on the refreshed release PR, remain required.
Only five files change: readiness workflow, helper/tests, root test command and contribution guidance. No publish workflow, permissions, secret, dependency or version changes. This is validation hardening, not hostile-PR process isolation.
No release is authorized by this PR. Keep #32 draft pending this fix, fresh candidate review, all expected checks and explicit publication approval.