docs: update release process for deterministic publish workflow#166
Open
docs: update release process for deterministic publish workflow#166
Conversation
Reflects the new publish-release-from-release-head workflow (INFRA-3250): production builds are now created from release branch HEAD before merging to stable, replacing the old automatic build triggered on stable merge. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Curious if at some point we should rename this file |
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.
Summary
Updates
docs/release-process.mdto reflect the new deterministic release workflow for MetaMask Extension (INFRA-3250, RAPID).What changed in the workflow:
tag-release-branchGitHub Action (which only added a tag) is replaced by the newpublish-release-from-release-headworkflow (manually triggered)stable, enforcingTag SHA == Build SHA == Release target SHAstableis now a sync step only — it no longer triggers an automatic production buildDiagram nodes updated:
CURRENT10:'Tag Release Branch' GitHub Action→'publish-release-from-release-head' workflowCURRENT11:Release tag is added on the release branch→Production build, tag, and GitHub release are created from release branch HEADSTABLE1:A new production build is automatically created and posted on the repo's releases page→Release branch is merged into 'stable' branchReferences