[cd] publish on release tags instead of branch push (#95085)
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. ## test plan 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 -->
Showing
Please
register
or
sign in
to comment