📝 add release workflow docs and cut-release.sh#4440
Draft
guiyanakuang wants to merge 1 commit into
Draft
Conversation
Phase 1 of #4439: introduces the documentation and helper script for the release-branch + dark-merge workflow. No CI changes yet. - doc/en/Releasing.md, doc/zh/Releasing.md: branch model, tag scheme, version property discipline, OSS / update channels, minor / patch / RC flows, mobile sync contract, rollback policy, checklist. - cut-release.sh: cuts release/X.Y from main and creates a chore branch on main that bumps the version properties to the next minor.
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
1 participant
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.
Closes #4439.
This is Phase 1 of the release workflow rework tracked in #4439: docs
and helper script only. CI is unchanged in this PR.
What's added
doc/en/Releasing.md+doc/zh/Releasing.md— full release workflow doc:branch model, tag scheme, version property discipline, OSS / update channels,
minor / patch / RC flows, mobile sync contract, rollback policy, checklist.
cut-release.sh— helper script that:main, clean tree, in sync with origin,properties version matches),
release/X.YfrommainHEAD and pushes it,main, creates achore/bump-to-X.(Y+1).0branch with the propertiesbump and pushes it (PR creation left manual on purpose),
What's NOT in this PR
The actual release flow described in
Releasing.mdwill only work end-to-endafter the CI changes land:
build-release.ymlbranch guard + RC tag pattern + channel-aware OSS pathvalidateAndUpdateVersion.jsenabling RC handlingdoc/MOBILE_COMPAT.mdinitializationEach of those will land as its own PR — see #4439 for the full rollout plan
and open questions.
Why draft
Opened as draft so the design can be reviewed and refined offline before any
of the wiring lands. The issue body has the full proposal; please leave
feedback there if anything in the model needs to change.