Fix release workflow credential handling#9
Merged
vedanthvdev merged 1 commit intomasterfrom Apr 16, 2026
Merged
Conversation
The plugin-publish 2.0+ natively reads GRADLE_PUBLISH_KEY and GRADLE_PUBLISH_SECRET environment variables, so passing them via -P flags is unnecessary. This also avoids exposing credentials in process arguments.
Merged
5 tasks
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
1 participant
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.
Summary
The
publishPluginsstep failed because the repository secrets haven't been added yet, andplugin-publish2.0+ natively readsGRADLE_PUBLISH_KEY/GRADLE_PUBLISH_SECRETenv vars — no need to pass them via-Pflags.Changes
./gradlew publishPluginswith env vars set (plugin reads them directly)Required: Add repo secrets
Go to Settings > Secrets and variables > Actions and add:
GRADLE_PUBLISH_KEYGRADLE_PUBLISH_SECRETOnce secrets are added and this PR is merged, the release workflow will work automatically for future merges.