Merged
Conversation
thomson-t
approved these changes
Mar 18, 2026
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.
Instructions
Summary
Add signing keys to smoke test
Note
Low Risk
Low risk workflow-only change; it only injects existing secrets into the Gradle smoke-test step and does not affect runtime code.
Overview
The release-draft GitHub Actions workflow now passes Maven Central in-memory signing credentials (
ORG_GRADLE_PROJECT_signingInMemoryKeyand...Password) into thepublishToMavenLocalsmoke-test step, aligning the local publish check with signed-release requirements.Written by Cursor Bugbot for commit 4fe1678. This will update automatically on new commits. Configure here.