Repository navigation
Stage PR #648 release-body remediation - #12
Merged
Merged
Conversation
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.
Purpose
Stage the production-intended remediation for
archzfs/archzfs#648 after updating
it to current production
master.The candidate merge commit has current production commit
926efc8as its firstparent and the existing production PR head
7ceed71as its second parent. Theconflict resolution preserves the current package/test architecture,
package-evidence guidance, corrected release description, current roadmap
review state, and staging procedure while integrating the release-body workflow
and keyring readiness gates.
Validation
actionlint1.7.12 with ShellCheck 0.11.0git diff --check origin/master...HEADasset, tag, title, release-state, or non-note release mutation.
<br>elements.The package-builder inputs and outputs are unchanged. The ordinary
Testworkflow is expected to run because workflow files changed; once it reaches the
builder step it can remain non-blocking under the repository's documented
long-check policy.
Staging result
The separately authorized default-branch metadata test completed successfully:
The push path changed notes to exactly match the body from current staging
master. After the body was replaced with a temporary sentinel, the no-opReleasecompletion causedworkflow_runreconciliation to restore the bodyfrom current staging
master.Across both paths, all assets and digests, annotated tags, title, release state,
release identity, failover state, and displayed
published_atremainedunchanged. No
_experimentalrelease or tag was created. The real packageReleaseworkflow remained manually disabled and no package publication ran.Cleanup restored the original staging body exactly, disabled the test-only
workflows, and returned staging
masterto production commit926efc8.The production-intended candidate remains on this branch; the staging-only
overlay is preserved separately at
experiment/pr-648-release-body-2026-09-18(267b753).GitHub records this PR as merged because staging
masterwas temporarilyfast-forwarded through the candidate for the authorized default-branch test.
The ordinary package Test remains non-blocking under the documented long-check
policy because this change does not affect its workflow, inputs, or outputs.