chore(ci): sync release-kit workflow from kits - #3221
Merged
Merged
Conversation
The next copy exists only to list the workflow in the Actions UI. It had drifted: it lacked the shrinkwrap prune step from #3085, so a stable release dispatched from next shipped dev entries and broke consumer npm ci under npm 10.
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
ajperel
approved these changes
Sep 28, 2026
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
2 participants
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.
Byte-for-byte copy of
.github/workflows/release-kit.yamlfrom the companionkitsPR (fix/release-kit-dist-tag). Thenextcopy exists only so the workflow appears in the Actions UI, but GitHub runs the steps from the dispatched ref, so drift here changes what gets published.This copy had drifted: it lacked the shrinkwrap prune step from #3085. firestore-bigquery-export@0.1.0 was dispatched from
nexttoday and shipped 101 dev lock entries including the@esbuild/*platform binaries, so consumernpm ciunder npm 10 fails withEBADPLATFORM. It also still rannpm dist-tag addafter a stable publish, which the trusted-publishing token cannot do (E401).Merge the
kitsPR first, then this one, and check the two files are identical afterwards. Not verified live.