Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Release process

Samuel D. Leslie edited this page Jun 2, 2022 · 5 revisions

Instructions assume a correctly configured development environment.

Preparation

  1. Determine the new version number (for subsequent steps).
  2. Update CHANGELOG.md (review the commit history).
  3. Push all commits on main and check all builds pass.

Releasing

  1. Update the version number in compare-api-java-client/pom.xml (but do not commit).
  2. Clean earlier build outputs: mvn clean
  3. Deploy a new release with Maven: mvn deploy -D publish -P release

Consult the internal documentation (Draftable employees only) for credentials suitable for publishing.

Post-release

  1. Increment the version number in compare-api-java-client/pom.xml and add a -SNAPSHOT suffix.
  2. Add a new Git tag corresponding to the release.
  3. Fast-forward the stable branch to match main.
  4. Update any internal repositories to use the new version.

Clone this wiki locally

Morty Proxy This is a proxified and sanitized view of the page, visit original site.