Bruno Borges 3384951fff Use gpg.passphraseEnvName instead of gpg.passphrase server ... The maven-gpg-plugin's `gpg.passphrase`/`passphraseServerId` mechanism is deprecated and fails when the plugin's `bestPractices` mode is enabled. Stop writing the `gpg.passphrase` server to settings.xml and instead set `gpg.passphraseEnvName` via an active profile when the configured passphrase env var name differs from the plugin default (MAVEN_GPG_PASSPHRASE). The default `gpg-passphrase` input value (GPG_PASSPHRASE) is unchanged, so the plugin reads the same environment variable as before. Fixes #760 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>		2026-07-14 21:54:47 -04:00
..
index.js	Use gpg.passphraseEnvName instead of gpg.passphrase server	2026-07-14 21:54:47 -04:00
package.json	Migrate to ESM and upgrade dependencies (#1078)	2026-07-08 10:15:00 +01:00