Audited changelog entries since last release
Public
Audited changelog entries since last release
Agent
Pi
Model
GPT-5.2 Codex
Started
Jan 30, 8:43 PM
Messages54
Downloads0
Reviewed changelog entries across packages.
UnderstandIdentified missing and duplicated changelog entries.
UnderstandRemoved irrelevant changelog entries.
Edit
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))Preparing to use tools and git tag
>git tag --sort=-version:refname | head -1>git log v0.50.5..HEAD --onelinePlanning changelog file reading
I need to fully read changelog files like packages/ai/CHANGELOG.md and analyze commits and stats with git show, while skipping docs-only changes.
Reviewing file read constraints
There's a conflict between the need to read the entire large changelog file before editing and the tool's 50KB truncation limit when reading without offset; the instructions forbid using offset for full reads, complicating acquiring the complete content before modification.
Resolving full read method
Decided to do an initial read without offset to capture as much as possible, then use offset-based reads to get the truncated remainder, effectively reading the full file despite instruction tension. Also preparing to inspect recent commits to determine relevant changelog entries, skipping doc-only or housekeeping commits.
>git show 39c898d7 --statAdding changelog entries
I'll add a user-facing changelog entry about the fixed terminal cursor hidden issue to both the tui and coding-agent changelogs, following the rule to duplicate relevant changes in both places.
>git show bb0c2bf7 --statSkipping non-informative commit
>git show 836e852a --statConfirming changelog duplication
The fix for terminal cursor hiding is in the tui changelog but missing in coding-agent, so I'll add it there for cross-package consistency.
>git show abd0c47b --statDeciding changelog updates
I'm planning to add a performance improvement note under "Changed" in both the TUI and coding-agent changelogs, since it likely affects end users despite being minor. Documentation updates do not need changelog entries.
>git show fd6c6d87 --statPreparing changelog update
>git show 0091857f --statChecking autogenerated model changes
The models.generated file shows 17 insertions likely from an autogenerated update tied to adding the [Unreleased] section, suggesting release housekeeping rather than functional changes; I’ll verify by reviewing the diff details.
>git show 0091857f --patch --statDeciding changelog updates for new model
The new AI package model should get an "Added" entry in ai's changelog and also a corresponding "Added" or "New Features" entry in coding-agent's changelog since it affects end users and follows cross-package duplication rules.
Clarifying changelog edit order and user proposal
The plan is to add missing changelog entries and insert an empty ### New Features section at the start of Unreleased in coding-agent, then propose the top new features to the user for confirmation before populating that section; to complete this properly, I need to finish reading the remaining part of the coding-agent changelog file.
Identifying missing changelog entries
I'm confirming prior changelog reads were complete and mapping specific commits to missing or existing changelog entries across ai, tui, and coding-agent. Next, I'll add the uncovered missing entries under appropriate sections like Fixed or Added.
Planning cross-package changelog edits
Decided to duplicate tui changelog fixes/changes into coding-agent with proper sections and attributions, plus add the AI model addition to both ai and coding-agent changelogs under Added. I'll insert a New Features header atop coding-agent Unreleased and ensure correct ordering and formatting before editing files.
we don't document models.generated.ts changes ...
Preparing to update changelog
I'll read the entire AI changelog file fully before removing the specified entry to ensure accurate updates.
Removed the models.generated entry from packages/ai/CHANGELOG.md. Anything else to adjust?
it was your job to evluate it changelog.md in any of the packages needs additional entries, or whetehr some entries need fixing
Providing audit summary with changelog notes
The audit reveals missing changelog entries for several commits, cross-package duplication where some tui fixes belong in coding-agent, and the need for proper external PR attribution with author format. It also proposes adding a "New Features" section highlighting top unreleased features like the extension API ctx.getSystemPrompt(), pending user confirmation before writing.
Preparing concise audit response with proposal
I'm summarizing that the new "### New Features" section needs adding after fixes in coding-agent, proposing top new features now for confirmation before writing, and noting the previously removed entry and formatting preferences.
Audit results since v0.50.5.
Missing changelog entries
Already covered or skipped
Cross-package duplication
New Features section proposal for coding-agent You asked me to propose before writing. Suggested items for ### New Features under packages/coding-agent/CHANGELOG.md:
Confirm this single entry or add more items you want in New Features, then I will insert the section and add the missing changelog entries.
git tag --sort=-version:refname | head -1git log <tag>..HEAD --oneline