[15.5.x] Release pipeline updates - #95161
Merged
eps1lon merged 5 commits intoJun 30, 2026
Merged
Conversation
(cherry picked from commit 618957c)
…94912) #94622 tried to be more strict with when a release is considered healthy. However, `@next/swc-wasm-web` is not enrolled in Trusted Publishing and blocks the release train. This PR restores the behavior for `@next/swc-wasm-*` packages prior to #94622 i.e. we continue the release train even if any `@next/swc-wasm-*` fails. Other NAPI bindings will continue to block the release train if they fail to publish. The bail vs no-bail behavior is controlled with a repository variable so that we can mor easily test if `@next/swc-wasm-web` is enrolled in Trusted Publishing. (cherry picked from commit 47c8c6f)
(cherry picked from commit b229f64)
That way we can push multiple commits when doing a release. For canaries, nothing will change. In a follow-up, we'll start cutting `@preview` from the `canary` branch. To support that case, we need to immediately revert the version in `lerna.json`. We shouldn't push commits indidually to avoid having an incomplete release if something else is pushed between `@preview` version bumps and `@canary` version reverts. After merge, the next canary release should publish from the `v…-canary.N` tag run (`deploy-target = production`), while the canary branch push for the same commit shows `skipped` — exactly one production run per release. <!-- NEXT_JS_LLM_PR --> (cherry picked from commit c8ff8b1)
(cherry picked from commit 1d09001)
Contributor
Tests PassedCommit: 35fc2f7 |
eps1lon
changed the title
eps1lon
marked this pull request as ready for review
June 25, 2026 12:32
bgw
approved these changes
Jun 29, 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
3 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.
Backports the following release-pipeline PRs from
canarytonext-15-5, one commit per PR. In the past, a diverging release pipeline had bugs that were blocking urgent releases. Generally, we should immediately backport release pipeline changes. Since the new pipeline has been tested (@next/swc-wasm-*is out,@previewis working), it's time to backport.@next/swc-wasm-*fails to publish #94912Convergence with canary
next-15-5carried an experimental, unused changesets-based release path. To keep a consistent release pipeline acrosscanary/next-16-2/next-15-5, these commits also discard it:changesets/action,pnpm ci:publish, Slack notification) and the legacyscripts/publish-native.jsstep__NEW_RELEASEenv and thenew-releasedeploy-target branchscripts/publish-release.js+ pnpm publish summary uploadAdapted for 15-5: native dir
crates/napi/npm(not canary'scrates/next-napi-bindings),next-15-5branch refs, and theRELEASE_CHECKvariable name.Leftover (not removed here):
.changeset/,scripts/release/*, and@changesets/*/ci:publishinpackage.jsonare now unused — can be cleaned up separately if desired.Not runtime-tested (release pipeline) — verified via
node --checkandprettier --check.test plan
Preparation regardless of release/semver type