All Versions
17
Latest Version
Avg Release Cycle
85 days
Latest Release
542 days ago

Changelog History
Page 1

  • v2.1.1 Changes

    December 02, 2020

    ๐Ÿš€ This is identical to 2.1.0, but Bintray keeps failing to publish ivy.xml for sbt-pgp 2.1.0, so here's a new release.

    ๐Ÿ‘ gpg 2 support

    ๐Ÿ‘ท sbt-pgp 2.1.1 adds support for gpg 2.1 and above. Previous to this fix, "Exit code: 2" was often reported on CI systems with gpg 2.1 and above:

    [error] gpg: signing failed: No such file or directory
    [error] gpg: signing failed: No such file or directory
    [error] java.lang.RuntimeException: Failure running 'gpg --batch --passphrase **** --detach-sign --armor --use-agent --output /some/output/file /some/input/file. Exit code: 2
    

    This is because --passphrase option requires --pinentry-mode loopback options as well, which is not compatible with gpg 1.4. To fix this, sbt-pgp will attempt to detect the version number. #184 by @eed3si9n

    note for automatic publishing

    ๐Ÿš€ In addition to sbt-pgp 2.1.1, sbt-ci-release will require a similar change. To workaround that create a file named .github/decodekey.sh

    #!/bin/bashecho $PGP\_SECRET | base64 --decode | gpg --batch --import
    
  • v2.1.0 Changes

    December 02, 2020

    2.1.0 failed to publish on Bintray, so please use 2.1.1 instead -

    [error] (plugin / publishSigned) error uploading to com.jsuereth/sbt-pgp/scala_2.12/sbt_1.0/2.1.0/ivys/ivy.xml: <html>
    [error] <head><title>405 Not Allowed</title></head>
    [error] <body bgcolor="white">
    [error] <center><h1>405 Not Allowed</h1></center>
    [error] <hr><center>nginx</center>
    [error] </body>
    [error] </html>
    
  • v2.1.0-M2

    December 02, 2020
  • v2.1.0-M1

    December 02, 2020
  • v2.0.2 Changes

    December 01, 2020

    ๐Ÿ–จ sbt-pgp 2.0.2 fixes the long-standing annoyance #174, which printed stderr messages from gpg CLI as [error] log.

    Before

    sbt:test> signedArtifacts
    [info] Wrote /path/to/sbt-pgp/src/sbt-test/sbt-pgp/credentials/target/scala-2.13/test_2.13-1.0.pom
    [error] gpg: using "..." as default secret key for signing
    [error] gpg: using "..." as default secret key for signing
    [error] gpg: using "..." as default secret key for signing
    [error] gpg: using "..." as default secret key for signing
    [success] Total time: 1 s, completed 2020/10/18 17:39:40
    

    After

    sbt:test> signedArtifacts
    [info] Wrote /path/to/sbt-pgp/src/sbt-test/sbt-pgp/credentials/target/scala-2.13/test_2.13-1.0.pom
    [info] gpg: using "..." as default secret key for signing
    [info] gpg: using "..." as default secret key for signing
    [info] gpg: using "..." as default secret key for signing
    [info] gpg: using "..." as default secret key for signing
    [success] Total time: 1 s, completed 2020/10/18 17:40:33
    

    This was contributed by Mitsuhiro Shibuya-san (@mshibuya) during ScalaMatsuri 2020 Day 2 OSS Hackathon.

  • v2.0.2-M1

    December 01, 2020
  • v2.0.1 Changes

    December 17, 2019

    โ†ช sbt-pgp 2.0.1 provides an workaround for gpg command running out of memory when multiple artifacts are signed concurrently #168 / #171 by @eed3si9n

  • v2.0.1-M3

    September 16, 2019
  • v2.0.1-M2

    September 16, 2019
  • v2.0.1-M1

    September 16, 2019