Reviewed changelog entries since last release.
UnderstandConfirmed readiness to commit changelog updates.
VerifyCommitted changelog changes.
EditPerformed patch release and published packages.
BuildAudit changelog entries for all commits since the last release.
Find the last release tag:
git tag --sort=-version:refname | head -1List all commits since that tag:
git log <tag>..HEAD --onelineRead each package's [Unreleased] section:
For each commit, check:
git show <hash> --stat)Description ([#N](url) by [@user](url))Cross-package duplication rule:
Changes in ai, agent or tui that affect end users should be duplicated to coding-agent changelog, since coding-agent is the user-facing package that depends on them.
Add New Features section after changelog fixes:
### New Features section at the start of ## [Unreleased] in packages/coding-agent/CHANGELOG.md.Report:
Sections (in order):
### Breaking Changes - API changes requiring migration### Added - New features### Changed - Changes to existing functionality### Fixed - Bug fixes### Removed - Removed featuresAttribution:
Fixed foo ([#123](https://github.com/badlogic/pi-mono/issues/123))Added bar ([#456](https://github.com/badlogic/pi-mono/pull/456) by [@user](https://github.com/user))Commits since v0.50.5: 8 commits
bb0c2bf7 - chore: approve contributor juanibiapina4b984734 - chore: approve contributor emanuelstfd6c6d87 - doc-only change (providers.md update)0091857f - release housekeeping (add [Unreleased] section)99281e59 - ctx.getSystemPrompt() ✓ (in coding-agent changelog with correct external contributor format)836e852a - cursor fix for #1099 ✓ (in tui changelog with external contributor format)| Commit | Description | Missing From |
|---|---|---|
39c898d7 | fix(tui): auto-clear empty rows when content shrinks (#1095) | tui, coding-agent |
abd0c47b | perf(tui): use startsWith short-circuit in isImageLine | tui (minor, internal) |
836e852a - tui cursor fix should be in coding-agent (affects end users)39c898d7 - tui content shrink fix should be in coding-agent (affects end users)Let me add the missing entries:
packages/tui/CHANGELOG.md:
### Changed section with isImageLine() optimizationpackages/coding-agent/CHANGELOG.md:
### Fixed section with cross-package duplications:
Looking at the commits since v0.50.5, there's only one addition (ctx.getSystemPrompt()) which is an API for extension developers, not a user-facing feature. This is already documented in the ### Added section.
There are no significant user-facing features in this release cycle that warrant a ### New Features section. The changes are primarily bug fixes:
ctx.getSystemPrompt())Should I still add a ### New Features section? If so, it would only contain the extension API addition, which might be better left in ### Added per the standard changelog format.
are we good to commit?
Done. Committed as d91cdc5f.
patch release
Released v0.50.6. All packages published to npm and tag pushed to GitHub.
git tag --sort=-version:refname | head -1git log <tag>..HEAD --oneline