Releasing New Versions

Preparation

1. Update the change log with meaningful descriptions, and links to PRs where appropriate
2. ./scripts/bump_version.sh {SemVerType} See SemVer compliant types.
3. If applicable, push the new branch and merge into master via a PR.
4. If a new major version or feature release, branch from master with the format {MAJOR_VERSION}-{MINOR_VERSION}-stable. If releasing a patch, cherry-pick commits onto the existing branch.
5. Create a new release thread to initiate the QA and release.

QA

1. Request the release candidate be deployed to the shelley_qa network Cardano Explorer instance for smoke testing the upgrade process. This may require coordination with a new version of the cardano-explorer-app, and should be specify in the request to the IOG SRE, informed by the development engineer in the release thread.
2. Perform any requested checks.
3. Request the release candidate be deployed to the testnet network Cardano Explorer instance, and state be refreshed if advised by the development engineer.

• https://explorer.shelley-qa.dev.cardano.org/
• https://explorer.cardano-testnet.iohkdev.io/

Release

1. Use the GitHub GUI to create a release draft and tag from the release branch, matching the version in package.json
2. Request sign-off from the required stakeholders.
3. The post-release workflow will build a Docker image for the version and deploy it to dockerhub.