Audited changelog and completed patch release
Public
Audited changelog and completed patch release
Agent
Pi
Model
Claude Opus 4.5 (latest)
Started
Jan 30, 8:47 PM
Messages48
Downloads0
Reviewed changelog entries since last release.
UnderstandConfirmed readiness to commit changelog updates.
VerifyCommitted changelog changes.
EditPerformed patch release and published packages.
Build
Audit 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))Let me start by finding the last release tag and then listing all commits since that tag.
>git tag --sort=-version:refname | head -1Now let me list all commits since that tag.
>git log v0.50.5..HEAD --onelineI have 8 commits since the last release. Let me categorize them:
39c898d7 - fix(tui): auto-clear empty rows when content shrinks (#1095)bb0c2bf7 - chore: approve contributor juanibiapina836e852a - Fixes #109999281e59 - feat(coding-agent): add ctx.getSystemPrompt() to extension contextabd0c47b - perf(tui): use startsWith short-circuit in isImageLine4b984734 - chore: approve contributor emanuelstfd6c6d87 - Update providers.md to include opencode provider (#1094)0091857f - Add [Unreleased] section for next cycleCommits to skip:
bb0c2bf7 - chore (contributor approval)4b984734 - chore (contributor approval)0091857f - release housekeeping (adding [Unreleased] section)Now let me read the changelog files and check the commit details for the non-skippable commits.
>git show 39c898d7 --stat>git show 836e852a --stat>git show 99281e59 --stat>git show abd0c47b --stat>git show fd6c6d87 --statNow I have all the information I need. Let me analyze each commit:
39c898d7 - fix(tui): auto-clear empty rows when content shrinks (#1095)
packages/tuibb0c2bf7 - chore: approve contributor juanibiapina
836e852a - Fixes #1099
packages/tui (CHANGELOG.md and src/tui.ts)@haoqixu, so it should have external contributor formatFixed terminal cursor remaining hidden after exiting TUI via \stop()` when a render was pending (#1099 by @haoqixu)`99281e59 - feat(coding-agent): add ctx.getSystemPrompt() to extension context
packages/coding-agentAdded \ctx.getSystemPrompt()` to extension context for accessing the current effective system prompt`abd0c47b - perf(tui): use startsWith short-circuit in isImageLine
packages/tui4b984734 - chore: approve contributor emanuelst
fd6c6d87 - Update providers.md to include opencode provider (#1094)
packages/coding-agent (docs only)0091857f - Add [Unreleased] section for next cycle
)- Not documented in tui CHANGELOG 2. **abd0c47b** -perf(tui): use startsWith short-circuit in isImageLine` - Not documented in tui CHANGELOG
ctx.getSystemPrompt() correctly documented in coding-agent changelog with external contributor attributionI need to add the missing entries to the tui CHANGELOG and ensure the cross-package fixes are reflected in both changelogs where applicable.
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:
Now I need to add the cross-package entries to coding-agent changelog. I need to add:
These should go in the Fixed section of the [Unreleased] part of coding-agent.
Now I need to propose a "New Features" section for coding-agent. Let me check what significant features were added since the last release. Looking at the commits:
ctx.getSystemPrompt() - This is a feature for extension developersThat's the only new feature since v0.50.5. The other changes are bug fixes or internal improvements.
Actually, looking at the task instructions again, I should propose the top new features for confirmation before writing them. The ctx.getSystemPrompt() is really an API addition for extension developers, not a user-facing feature.
Let me check if there's anything significant that warrants a "New Features" section. Looking at the commits again:
ctx.getSystemPrompt() - API for extensions (already in Added)There isn't really a major user-facing new feature in this cycle. The ctx.getSystemPrompt() addition is already documented in the Added section.
I should report this to the user rather than force a "New Features" section when there aren't any significant user-facing features.
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?
The user is asking if we're ready to commit. Let me verify the changes are correct and complete.
Looking at what was done:
The changes look correct. I should commit only the files I modified.
>git statusGood, only the two changelog files I modified are showing as changed. Let me commit them with a descriptive message.
>git add packages/coding-agent/CHANGELOG.md packages/tui/CHANGELOG.md && git commit -m "docs: add missing changelog entries for v0.50.5..HEAD
- tui: add #1095 content shrink fix (by @marckrenn)
- tui: add isImageLine perf optimization
- coding-agent: cross-package duplication for #1095, #1099"The commit succeeded. The pre-commit hooks showed some lint warnings/infos but nothing blocking - those are pre-existing issues in other files, not related to my changes.
Done. Committed as d91cdc5f.
patch release
The user wants to do a patch release. According to the AGENTS.md, I should run npm run release:patch.
>npm run release:patchThe release was successful. Published v0.50.6 with all the changelog entries in place.
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