Repository navigation
ci: reuse prerelease verification and support skip-release - #11
Merged
Merged
Conversation
ElgoogUdiab
marked this pull request as ready for review
September 23, 2026 16:18
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.
The same CLI changes currently run the full six-environment matrix at both PR stages and both publication stages. Promotion PRs and main pushes now reuse a successful prerelease Release run only when its exact commit has the same complete Git tree as the proposed release. Missing evidence, API failures, changed contents and unsupported merge shapes fall back to full CI. Development PRs and prerelease pushes retain the full matrix.
Formatting and lint run once per full verification. All six environments still compile with TypeScript through
npm test, so the redundant standalonetsc --noEmitstep is removed. Existing required checks and publication installation checks remain in place.A
skip-releaselabel on the PR merged by a push suppresses npm publication and GitHub Release creation on either release branch, while verification continues. The label does not carry over from an earlier development PR. Unavailable or ambiguous PR metadata blocks publication. This PR carries the label to avoid publishing a beta for CI maintenance.Validation: lint, formatting and actionlint passed; 52 existing repository tests and five local workflow regression tests passed; npm global/local/one-off, pnpm and Yarn packed installations passed. The workflow regression tests remain local and are not included in this PR.