[ci]: add workflow to bump canary after backport#92801
Merged
ztanner merged 2 commits intoApr 15, 2026
Merged
Conversation
Contributor
Tests Passed |
ztanner
force-pushed
the
04-14-_ci_add_workflow_to_bump_canary_after_backport
branch
from
0b7bfd1 to
9d32f22
Compare
ztanner
force-pushed
the
04-14-_ci_add_workflow_to_bump_canary_after_backport
branch
from
9d32f22 to
4c0a03b
Compare
Contributor
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URL |
ijjk
approved these changes
Apr 14, 2026
|
Many thanks for fixing this!
It has been rather frustrating dealing with unforgiving/rigid enterprise security tooling that (understandably) assumes, e.g., v16.2.1-canary.42 is older than v16.2.3 when it is actually newer! The security tools rely on semver ranges defined in GHSAs like GHSA-q4gf-8mx6-v5v3 , which has |
eps1lon
approved these changes
Apr 15, 2026
ztanner
force-pushed
the
04-14-_ci_add_workflow_to_bump_canary_after_backport
branch
from
6a6c716 to
cb29b62
Compare
ztanner
deleted the
04-14-_ci_add_workflow_to_bump_canary_after_backport
branch
This was referenced Apr 23, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 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.
This adds an automated path to keep canary semver-ahead after a successful stable backport publish.
Today, a backport release can produce a stable version that is newer than the current canary version, which creates confusing version ordering for tooling. This change adds a follow-up workflow that evaluates completed backport publishes and, when appropriate, triggers a canary preminor release on canary.
The
Sync Canary After Backport Releaseworkflow evaluates whether a completedbuild-and-deployrun should trigger a canary sync.The evaluation only triggers when:
Potentially publish releasejob succeededWhen all checks pass, the workflow dispatches trigger_release.yml on canary with:
(This is currently gated behind an env flag so we can dry-run it)