RELEASING.md

Publish a New Release

Create a New Release

1. Ensure all tests pass & CI indicates that the status is green.
2. Update VERSION_NAME in gradle.properties.
3. Create a new commit for the version number change, naming it Bump version to x.y.z.
4. Tag that commit as vx.y.z (must match v[0-9]+.[0-9]+.[0-9]+).
5. Push all commits & tags to GitHub.

Publish to Maven Central

Confirm that the gradle.properties file in the home directory (~/.gradle/gradle.properties) is present and set up correctly.

./gradlew publish

Close & Release Manually

Manually

Assuming ./gradlew publish has been run after a new version has been released.

• Go to https://oss.sonatype.org/#stagingRepositories, login as chimbori.
• Select the comchimboricrux-xxxx repo
• Click on Close from the top toolbar, wait for it to complete.
• Click on Release from the top toolbar.

Set Up Key Signing on a New Machine

Signing

1. Install GPG, e.g. brew install gpg on macOS.
2. Locate stored credentials from private storage.
3. Run restore-keys.sh from the stored credentials directory.
4. Enter the password for chimbori when prompted. This password is different from the Sonatype/Nexus password.

Credentials

1. Copy gradle.properties.sample to ~/.gradle/gradle.properties and fill in the missing redacted credentials.
2. If gradle.properties.private exists, it may be used instead. gradle.properties.private is configured to be .gitignored, so make sure it is never pushed to a public repo.
3. The new machine is now ready and configured for pushing to Maven Central.