You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 53a7fc4
Browse filesBrowse the repository at this point in the historyBrowse files
feat(release): cutting an rc freezes the line into release-X.Y
Cutting the first vX.Y.0-rc.N now creates release-X.Y at the tagged
commit, and every later cut for that line must be dispatched from the
branch — a dispatch from main is refused.
Before this, only the stable promote-PR merge created release-X.Y, so
rc.2 and rc.3 were cut from main's tip and silently picked up every
feature merged since rc.1. The release therefore shipped content no rc
had ever validated. Freezing at the rc closes that: main stays open for
the next minor, and fixes reach the release by cherry-pick onto the
branch.
promote-rc.yaml needs no change — it already prefers release-X.Y as the
promote PR base when that branch exists, so the stable release is now
cut from the frozen tree.
Gated to -rc (alpha/beta are pre-freeze builds off an open main) and to
patch 0 (a patch-line rc is cut from a release-X.Y that already exists).
The branch is create-only and never force-moved: moving it would re-open
the freeze and drag in whatever the new tip holds.
Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>
echo "::error::release-$LINE already exists — the $LINE line is frozen. Cut v$LINE.* from 'release-$LINE' (cherry-pick fixes there first); 'main' is open for the next minor."
197
+
exit 1
198
+
elif [ "$rc" -ne 2 ]; then
199
+
echo "::error::Could not query origin for release-$LINE (git ls-remote exit $rc) — refusing to proceed."
200
+
exit 1
201
+
fi
202
+
166
203
- name: Cut and push the pre-release tag
167
204
env:
168
205
TAG: ${{ steps.parse.outputs.tag }}
@@ -222,3 +259,40 @@ jobs:
222
259
git push origin "HEAD:refs/tags/$TAG"
223
260
echo "Pushed $TAG at $local_head from '$REF_NAME'."
224
261
echo "tags.yaml will now build and draft the pre-release and create its staging branch; rc tags also run mandatory full E2E."
262
+
263
+
# Freeze the line. An rc is the feature-freeze signal, so the first
264
+
# vX.Y.0-rc.N branches release-X.Y at the tagged commit. From here the
265
+
# release's content is closed: fixes reach it only by cherry-pick or
266
+
# backport onto the branch, while 'main' moves on to the next minor.
267
+
# promote-rc.yaml then targets its promote PR at release-X.Y (it already
268
+
# prefers that branch when it exists), so the stable release is cut from
269
+
# the frozen tree rather than from whatever main has accumulated.
270
+
#
271
+
# Gated to -rc: alpha/beta are pre-freeze validation builds cut from an
272
+
# open main, and freezing on them would force every later change onto
273
+
# cherry-picks far too early.
274
+
#
275
+
# Gated to patch 0: a patch-line rc (vX.Y.Z-rc.N, Z>0) is cut from
276
+
# release-X.Y, which by definition already exists.
277
+
#
278
+
# Create-only, never force-moved — a later rc.N finds the branch and
279
+
# no-ops. Moving it would silently re-open the freeze and drag in
280
+
# whatever the new tip contains, defeating the whole mechanism.
0 commit comments