Audited changelogs and completed patch releasePublic

Agent

Model

GPT-5.2 Codex

Started

Jan 26, 10:58 PM

Messages119

Downloads0

Summary

Closed, Completed

Understand
Reviewed changelog entries since last release.
Understand
Edit
Committed and pushed changelog updates.
Edit
Verify
Confirmed readiness for patch release.
Verify
Build
Completed patch release and published new version.
Build

What module(s) should I work on?

Audit changelog entries for all commits since the last release.

Process

Find the last release tag:

List all commits since that tag:
bash
```
git log <tag>..HEAD --oneline
```
Read each package's [Unreleased] section:
- packages/ai/CHANGELOG.md
- packages/tui/CHANGELOG.md
- packages/coding-agent/CHANGELOG.md
For each commit, check:
- Skip: changelog updates, doc-only changes, release housekeeping
- Determine which package(s) the commit affects (use git show <hash> --stat)
- Verify a changelog entry exists in the affected package(s)
- For external contributions (PRs), verify format: 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:
- Insert a ### New Features section at the start of ## [Unreleased] in packages/coding-agent/CHANGELOG.md.
- Propose the top new features to the user for confirmation before writing them.
- Link to relevant docs and sections whenever possible.
Report:
- List commits with missing entries
- List entries that need cross-package duplication
- Add any missing entries directly

Changelog Format Reference

Sections (in order):

### Breaking Changes - API changes requiring migration
### Added - New features
### Changed - Changes to existing functionality
### Fixed - Bug fixes
### Removed - Removed features

Attribution:

Internal: Fixed foo ([#123](https://github.com/badlogic/pi-mono/issues/123))
External: Added bar ([#456](https://github.com/badlogic/pi-mono/pull/456) by [@user](https://github.com/user))

Report

Missing changelog entries found and added

ee7d03cf fix(coding-agent): prune empty git dirs on remove. Added to packages/coding-agent/CHANGELOG.md under [Unreleased] Fixed.
3ae0cbe3 fix(coding-agent): Title Case extension hotkeys in /hotkeys output (#969). Added to packages/coding-agent/CHANGELOG.md under [Unreleased] Fixed with PR attribution.
9f3eef65 fix(ai): filter deprecated OpenCode models from generation (#970). Added to packages/ai/CHANGELOG.md under [Unreleased] Fixed with PR attribution. Duplicated in packages/coding-agent/CHANGELOG.md per cross-package rule.

Commits that do not need entries

3c252d50 docs(coding-agent): doc-only change.
2bbc1a76 changelog housekeeping.
a5f603d7 fix(diff): change is in .pi/extensions/diff.ts, not part of the packages you listed.

Cross-package duplication

Added the OpenCode Zen deprecated model filtering fix from ai to coding-agent.

Changelog updates made

packages/ai/CHANGELOG.md
packages/coding-agent/CHANGELOG.md

New Features section

Inserted ### New Features at the start of ## [Unreleased] in packages/coding-agent/CHANGELOG.md.
I did not add any bullets yet. There were no new feature commits since v0.50.0. Confirm if you want to keep it empty or provide feature highlights to add with doc links.

any new features since the last release?

No. Since v0.50.0 the commits are fixes and a doc-only change. No new features.

then remove the ### new feature section

Removed ### New Features from packages/coding-agent/CHANGELOG.md.

commit and push those changes to the changel.md files, do not commit the changes to @packages/coding-agent/docs/packages.md

Committed and pushed changelog updates for:

packages/ai/CHANGELOG.md
packages/coding-agent/CHANGELOG.md

Left packages/coding-agent/docs/packages.md uncommitted as requested.

ready for a patch release?

Not yet. There is still an uncommitted change:

packages/coding-agent/docs/packages.md

If that change is intentional and should remain uncommitted, we can proceed with the release steps. Otherwise, tell me whether to commit or discard it.

it's commited and pushed, do a patch release

Patch release completed. Published v0.50.1 packages, pushed commits to main, and pushed tag v0.50.1. Working tree is clean.

exit