Publishing

Publishing

• Relies on Github Actions CI/CD
• snapshot versions are automatically signed and published to OSS sonatype snapshots repo - https://oss.sonatype.org/content/repositories/snapshots/com/github/pjfanning/jackson-caffeine-cache/
• releases should work via Github Actions CI/CD but none have yet be done that way (next one hopefully)
  • change version in build.gradle to release number (without a SNAPSHOT suffix)
  • git commit
  • tag the commit with a tag with the release number prefixed by 'v'
  • git push
  • You'll need to use OSS Sonatype UI to complete the release of the staging repository

Github Actions CI/CD secrets

• SONATYPE_USERNAME - user token generated username or real username (https://github.com/sbt/sbt-ci-release#optional-create-user-tokens)
• SONATYPE_PASSWORD - user token generated password or real password
• PGP_PASSPHRASE - password for your secret key
• PGP_SECRET - ASCII armored secret key
  • https://stackoverflow.com/questions/57921325/gradle-signarchives-unable-to-read-secret-key
  • gpg --armor --export-secret-keys $LONG_ID

Gradle

• https://docs.gradle.org/current/userguide/signing_plugin.html#sec:in-memory-keys
• https://docs.gradle.org/current/userguide/publishing_maven.html
• https://github.com/gradle-nexus/publish-plugin