Repository navigation
ci: run Maven Central publish in release environment - #168
Merged
Merged
Conversation
Restricts the signing key and Sonatype credentials to v* tag refs once they are moved to the environment. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
anush008
approved these changes
Oct 21, 2026
Member
|
@generall, sorry, I merged out of habit. |
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.
Adds
environment: releaseto thepublishjob. Thereleaseenvironment only allowsv*tags.Maven Central has no trusted publishing, and the GPG signing key has to stay a secret, so the 5
ORG_GRADLE_PROJECT_*secrets move into the environment instead of being removed.Safe to merge before the secrets are moved: a job in an environment still sees repo secrets.
🤖 Generated with Claude Code