Skip to content

ci(release): use setup-java's *-env-var inputs - #498

Merged
kingchenc merged 1 commit into
mainfrom
ci/setup-java-env-var-inputs
Oct 31, 2026
Merged

kingchenc merged 1 commit into
mainfrom
ci/setup-java-env-var-inputs

Conversation

@kingchenc

Copy link
Copy Markdown
Collaborator

actions/setup-java deprecated three inputs of the Maven Central step in release.yml, and every release run that still uses them carries a warning annotation:

deprecated replacement
server-username server-username-env-var
server-password server-password-env-var
gpg-passphrase gpg-passphrase-env-var

The action.yml of both pinned releases (v6.0.1 and v6.1.0) declares the old names as "Deprecated alias for" the new ones. Both take the name of an environment variable, not a secret, so the values (CENTRAL_USERNAME, CENTRAL_PASSWORD, GPG_PASSPHRASE) stay as they are and the generated settings.xml is identical.

release.yml runs on tag pushes only, so this PR's checks cover it through actionlint and zizmor; the next release run is where the warnings disappear.

setup-java deprecated server-username, server-password and gpg-passphrase
in favour of server-username-env-var, server-password-env-var and
gpg-passphrase-env-var, and warns on every release run that still uses
them. The old names are aliases with the same meaning -- the name of the
environment variable the Maven deploy step sets -- so the values stay as
they are and settings.xml comes out identical.
@codecov

codecov Bot commented Oct 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@kingchenc
kingchenc merged commit 90ca39c into main Oct 31, 2026
66 checks passed
@kingchenc
kingchenc deleted the ci/setup-java-env-var-inputs branch October 31, 2026 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant