Announce: sbt-pgp 2.0 beta release

I released sbt-pgp 2.0.0-M2 for sbt 0.13 and sbt 1.x. This is a beta release for sbt-pgp 2.0.

Consider migrating to sbt-gpg

sbt-pgp has not been well maintained over the years, and there’s a growing feature disparities between the pure Java Bouncy Castle implementation and GnuPG (gpg). sbt-pgp supports both implementations, but sbt-pgp 1.x has been defaulting to Bouncy Castle implementation.

sbt-gpg is a new plugin that is being developed by Jakob Odersky that is designed around using gpg. We encourage you to try sbt-gpg, and report/fix any issues found in the plugin.

Breaking change: useGpg by default

In an effort to provide smooth transition towards sbt-gpg, I am flipping the default setting useGpg to true so it assumes that you have installed gpg on your local machine.

On CI environment etc, if you still need the old features (like passing passphrase around), you can override this using the system property SBT_PGP_USE_GPG:

$ sbt -DSBT_PGP_USE_GPG=false

Since this is a biggish change in the behavior, I am bumping the major version number. Please try it, and report and/or help us fix any errors.

Breaking change: camel case key name

sbt-pgp 1.x had camelCase in the build.sbt, but kebab-case in the sbt shell.
sbt-pgp 2.0.0 unifies them to camelCase.

pinentry support

Adds a pinentry option to sbt-pgp, by using the --pinentry-mode loopback option.

Adds a useGpgPinentry boolean key that if set with useGpg and useGpgAgent set, will use a specialized signer CommandLineGpgPinentrySigner. by @wsargent

Fixes the pgpSecretRing default

Fixes the “Exit code: 2” error on gpg by fixing the default value for pgpSecretRing. by @eed3si9n