Repository navigation
ci: add release gates and pin workflow actions - #269
Draft
ffumero2003 wants to merge 11 commits into
Draft
ffumero2003 wants to merge 11 commits into
ffumero2003 wants to merge 11 commits into
Conversation
Contributor
Author
Snyk Code (
|
ffumero2003
force-pushed
the
release-standard-conformance-workflows
branch
10 times, most recently
from
November 19, 2026 15:41
757b613 to
fa5bb43
Compare
Check the signed-tag, milestone, and security commands in the release-checks job and the weekly root Actions update entry. Preserve the original eight workflow mutations and add four removal probes for these checks.
…se gates Query generic secret patterns explicitly and omit secret values from both alert responses. Cover pagination, inaccessible responses, and every supported generic pattern. Retain registered hardware-backed SSH public keys in the allowed-signers input while keeping real signature verification and the fixed signer principal.
Execute the workflow metadata step against immutable Git fixtures, requiring tag/version and changelog agreement while ignoring uncommitted local metadata. Add a mutation that removes the validation command and strengthen the workflow contract to detect it. Keep all existing workflow mutations.
ffumero2003
force-pushed
the
release-standard-conformance-workflows
branch
from
November 19, 2026 15:51
fa5bb43 to
745b250
Compare
Exercise signed-tag verification with the repository's default maintainer registry and assert each intended account's key endpoints are consumed. Check the unrestricted changelog pull-request trigger and mutation-test restoration of the old branch filter.
Check that the deployment job runs a real Gradle build before Maven publication, and prove removal of the build command fails the workflow contract.
ffumero2003
marked this pull request as draft
November 19, 2026 16:30
Contributor
Author
|
Converting to draft and parking this (stacked on #268). On hold pending internal coordination on this repo's release-process ownership; work preserved to revisit later. Not for merge in the meantime. |
This branch has not been deployed
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.
Context
Tag-triggered publication needs explicit release checks, immutable action revisions, and release notes drawn from the reviewed changelog. This PR is stacked on #268 (
release-standard-conformance). After #268 is squash-merged, rebase only this branch's workflow commits onto the updatedmaster, then retarget this PR tomaster.Changes
gh release create --notes-fileusing the exact version changelog section.master, validate the Gradle/changelog version and complete version milestone, and build that same commit. Require readable security data and hold for medium/high/critical findings, open secret alerts, or unscored active advisories.ENFORCE_SIGNED_TAGS=trueenables enforcement after enrollment. Disposable fixture keys exist only during tests.--dry-runand placeholder credentials; use a fixed principal for registered SSH signing keys, independently of tagger metadata. Document the ordinary token’s checkout, signing-key lookup, milestone, and release uses.The Maven Central publishing command, GPG artifact-signing secrets, Gradle publication configuration, and Sonatype staging endpoint/tasks remain unchanged. OIDC is used for Pages only.
Before merging this PR, switch Pages to GitHub Actions and configure the
github-pagesenvironment. Before the first tagged release, provision the documented read-only security token/source access and complete the release-owner TODO for the Maven artifact-signing trust source and independent primary-fingerprint confirmation. No production artifact-signing fingerprint is approved in this change. Signed-tag verification remains warn-only until maintainers enroll their keys andENFORCE_SIGNED_TAGS=trueis deliberately enabled.Verification
./gradlew build --no-daemonpassed.scripts/tests/test_workflow_mutations.py, including unchanged baselines and assertion failures for the original eight workflow cases plus signed-tag, milestone, security, and Dependabot entry removals, plus removal of metadata validation and restoration of restricted changelog PR branches and removal of the release build command. A real Git fixture executes that metadata step against the event commit and rejects tag/version and changelog mismatches. The default maintainer-registry test confirms all three intended accounts are consumed; disposable added/removed-maintainer mutations fail.actionlint, shell syntax, changelog consistency, and whitespace checks passed. The public Pages status API returnedoperationalthrough the replacement command.--dry-run; all publishing operations were skipped. No production release was attempted.RELEASE_READ_TOKENand source access must be configured before publishing. Pages must be switched to GitHub Actions before the new Pages deployment is used.Closes #267