Repository navigation
ci: add release gates and pin workflow actions - #269
Open
ffumero2003 wants to merge 3 commits into
Open
ffumero2003 wants to merge 3 commits into
ffumero2003 wants to merge 3 commits into
Conversation
Contributor
Author
Snyk Code (
|
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.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. Signed-tag verification remains warn-only until maintainers enroll their keys andENFORCE_SIGNED_TAGS=trueis deliberately enabled.Verification
./gradlew build --no-daemonpassed.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