Solo Release Checklist

1. Verify Workflows

2. Validate Documentation Site

3. Compare Changes Since Last Release

4. Determine Next Version

  • Review commit messages
  • Follow commit message conventions from PR template
  • Alternatively:
    • Run release workflow with dry-run to determine version

5. Review Migration Impact

  • Inspect changes in /data folder:
    • Local config migrations
    • Remote config migrations
  • Confirm migration scenarios are covered
  • Assess impact on:
    • Helm chart upgrades
  • Decide version bump:
    • Patch / Minor / Major

6. Update Documentation (Skip if PATCH)

  • Create PR updating:
    • README.md
    • docs/legacy-versions.md
  • Include:
    • New Solo version
    • Helm chart version
    • CN / Hedera versions
    • Release date
    • End of support:
      • Odd versions → 1 month
      • Even versions → 3 months
  • Get approval and merge PR

7. Run Release Workflow

8. Update npm latest Tag (Manual)

⚠️ Requires npm access

  • npm dist-tag add @hashgraph/solo@ latest

9. Verify npm Package (@hashgraph)

10. Verify JFrog Artifactory (@hashgraph)

11. Verify npm Package (@hiero-ledger)

12. Verify JFrog Artifactory (@hiero-ledger)