Solo Release Checklist
1. Verify Workflows
- Check that the last merge to
mainpassed all workflows:
2. Validate Documentation Site
- Review deployed docs:
- Check other key pages for correctness
- Note: Site updates automatically on PR merge to
main
3. Compare Changes Since Last Release
- Compare latest tag with
main:
4. Determine Next Version
- Review commit messages
- Follow commit message conventions from PR template
- Alternatively:
- Run release workflow with
dry-runto determine version
- Run release workflow with
5. Review Migration Impact
- Inspect changes in
/datafolder:- 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.mddocs/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
- Workflow:
- Settings:
- Use workflow from:
main - Dual publish:
true - Dry run:
false
- Use workflow from:
8. Update npm latest Tag (Manual)
⚠️ Requires npm access
- npm dist-tag add @hashgraph/solo@
latest