Bruno Borges 0d4af386ec Keep GPG_PASSPHRASE default for v5 compatibility ... Revert the gpg-passphrase input default back to GPG_PASSPHRASE so existing v5 workflows that set the GPG_PASSPHRASE environment variable keep working without changes. setup-java writes gpg.passphraseEnvName=GPG_PASSPHRASE into an active profile, so the maven-gpg-plugin reads the same variable as before. The only remaining compatibility requirement is maven-gpg-plugin 3.2.0+, which is documented in the README and advanced usage guide. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7d0a510e-aebf-4ec4-a667-efeb3e4edeb1		2026-07-14 22:26:12 -04:00
..
adrs	Spelling (#713)	2026-06-22 10:57:54 -04:00
advanced-usage.md	Keep GPG_PASSPHRASE default for v5 compatibility	2026-07-14 22:26:12 -04:00
contributors.md	chore: enforce pre-PR validation (aggregate scripts, git hooks, PR checklist) (#1061)	2026-06-26 08:07:16 +01:00
switching-to-v2.md	Fix typo in documentation "jdkfile" (#167)	2021-04-14 11:33:57 +03:00