feat(releases): add semantic release orchestration - #53
Merged
Conversation
Pull Request Summary by devActivityMetricsAchievements
|
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
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 #47.
What this adds
verify-release-planaction for Aetheregohygiene.repository-release/v1declarationsrelease-prepare.ymlworkflow for pull-request or manual reviewsemantic-release.ymlhandoff that re-verifies before invoking the existing immutablerelease-artifact.ymlRegistry publication, container pushes, site deployment, DOI/archive submission, and product credentials remain repository-owned adapters. Ordinary pull requests cannot reach publication because the immutable release workflow rejects every event except an explicit default-branch push or manual dispatch.
Relay release preparation
This PR prepares Relay
v1.5.0inrelease.jsonandCHANGELOG.md, but does not publish it. After merge, the repository's explicit manualrelease.ymldispatch will build thegithub-actionprofile bundle and dogfood the new reusable handoff.Validation
github-actionprofile bundle validationRuby/actionlint are unavailable locally, so required GitHub CI remains responsible for the native Actions/YAML workflow graph validation. Relay #6 remains open for the broader organization-wide durable-report rollout; this PR implements the release-specific evidence boundary required by #47.