Skip to content

chore(ci): use setup-java env-var inputs for Maven credentials - #454

Merged
manusa merged 1 commit into
mainfrom
chore/setup-java-env-var-inputs
Nov 1, 2026
Merged

manusa merged 1 commit into
mainfrom
chore/setup-java-env-var-inputs

Conversation

@manusa

@manusa manusa commented Nov 1, 2026

Copy link
Copy Markdown
Owner

Summary

actions/setup-java@v6 has deprecated the server-username, server-password and gpg-passphrase inputs. Its action.yml now calls them "Deprecated alias for …-env-var". The v0.0.22 release run (41277699804) logged a warning for each of them:

The 'server-username' input is deprecated and may be removed in a future release. Please use 'server-username-env-var' instead.

This PR renames the three inputs to server-username-env-var, server-password-env-var and gpg-passphrase-env-var in:

  • .github/workflows/release.yml
  • .github/workflows/snapshots.yml

The values stay the same: the names of the environment variables (MAVEN_CENTRAL_USERNAME, MAVEN_CENTRAL_PASSWORD, SIGNINGPASSWORD) that the deploy step sets from secrets. setup-java still writes them to settings.xml as ${env.X} placeholders, so publishing to Central works the same way.

Testing

The PR build does not run either changed workflow. After merge, the nightly snapshots.yml run (cron 02:00 UTC, or a manual workflow_dispatch) will confirm the change before the next release. Look for the deprecation warnings to be gone and for the snapshot deploy to authenticate and sign as before.

actions/setup-java v6 deprecated server-username, server-password and
gpg-passphrase in favor of the -env-var variants. The release run for
v0.0.22 warned about each one. Rename them in the release and snapshot
workflows. The new inputs take the same environment variable names, so
the generated settings.xml stays the same.

Co-authored-by: Claude Opus 5.5 <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>
@manusa
manusa merged commit 171bc33 into main Nov 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant