ci: align release gates with browser lanes - #20
Merged
Merged
Conversation
Run package, browser smoke, and retrieval verification before tag publication. Avoid duplicate publish lifecycle scripts and move delivery actions to Node 24-compatible majors.
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.
What changed
prepublishOnly, browser smoke, and retrieval evaluationWhy
pnpm testis now intentionally non-browser, so the tag workflow otherwise could publish without real-browser smoke. Existing Action majors also emitted Node 20 runtime deprecation warnings.Impact
Performance timing tests remain scheduled/manual and do not block releases. Project tests still run on Node 22.13; only the Actions' internal runtimes change.
Verification
git diff --check: passedNo tag, npm publication, GitHub release, or merge was performed.