docs: document automated release workflow - #96
Closed
vitormattos wants to merge 10 commits into
Closed
vitormattos wants to merge 10 commits into
vitormattos wants to merge 10 commits into
Conversation
vitormattos
changed the title
Member
Author
|
Release automation scope has now been consolidated in #97. Before this documentation PR is considered final, the release guide should be aligned with that issue and the implemented workflow. In particular, avoid growing a single long page indefinitely: keep a short maintainer journey/overview and split detailed policy or manual recovery into focused developer pages when that improves navigation. The public docs must describe both the normal GitHub Actions path and the equivalent manual/CLI procedure, and they must stay in the same development cycle as release behavior changes. |
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.
Summary
Documents the sequenced, CLI-driven release automation proposed in LibreSign/libresign#8447.
The release workflow files are now ordered explicitly:
release-00-tests.yml— Release 00 - Automation testsrelease-10-prepare-pr.yml— Release 10 - Prepare release PRrelease-20-finalize-preparation.yml— Release 20 - Finalize preparationrelease-30-prepare-draft.yml— Release 30 - Prepare draftrelease-40-publish-appstore.yml— Release 40 - Build, sign and publish App StoreThe documentation explains that LibreSign-specific release logic lives in
scripts/release/behind therelease.phpCLI, while the YAML files primarily orchestrate actions and CLI commands.It also documents:
actis useful for development but not authoritative