Automated releases replace manual versioning
GitHub repositories can now compute release versions automatically from commit messages. A bot opens a release PR, maintainers review and merge, and CHANGELOGs generate themselves.
Release engineering just got a lot less tedious. Instead of manually typing version numbers into a GitHub Actions workflow, maintainers can now write conventional commit titles and let release-please handle the rest. The bot reads commit titles since the last tag, computes the appropriate bump (major for breaking changes, minor for features, patch for fixes), opens a release PR for review, and creates tags and GitHub Releases on merge.
A companion workflow flags non-conventional PR titles as a visible status check. This prevents commits from silently skipping the CHANGELOG — if a title doesn't follow the feat:, fix:, chore: convention, it shows up clearly so maintainers can fix it before merge.
The old manual release workflow stays in place as a hotfix escape hatch. Projects that need to ship a specific version without waiting for release-please's PR cycle can still go to Actions → Release → Run workflow.
In the project, this touches the release tooling and documentation. Workspaces remain at 0.0.0 since they're private and never published — only the root package gets version bumps.