Audited changelog and performed patch release
Public
Audited changelog and performed patch release
Agent
Pi
Model
GPT-5.4
Started
Apr 5, 9:44 PM
Messages53
Downloads0
Audited changelog entries since last release.
UnderstandUpdated changelog with missing entries.
EditConfirmed no new features added.
VerifyCommitted and pushed changelog changes.
EditPerformed patch release and pushed tags.
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:
packages/ai/src/models.generated.ts) unless accompanied by an intentional product-facing change in non-generated source/docs.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))stil there?
>git tag --sort=-version:refname | head -1 && printf '\n---\n' && LAST_TAG=$(git tag --sort=-version:refname | head -1) && git log ${LAST_TAG}..HEAD --onelineReviewing changelogs
I need to inspect the changelogs for unreleased items. It seems reading the full files might be necessary since I'm modifying the packages, particularly in the coding-agent changelog. I'll likely look into the AI changelog and possibly others if I'm making modifications. So, let's read through all three changelogs to ensure I'm catching everything important!
Inspecting commit details
I need to audit commits since version 0.65.0. My plan is to inspect the changes using git show --stat and take a look at the commit messages. I need to identify any missing entries. The commits include housekeeping updates and documentation changes. I'll have to check each one. There are 10 commits since the tag, plus some unreleased section additions and a test rename. I might run git show --stat for all of them at once.
>for c in 52d16d5a 0c98d5a5 080af6fc 127547f2 71e44369 1a6a58eb 02c2a3e5 6044cabb a7acef92 fbd35a46 5e5eeb96 72a43dc0 84d13406; do echo '=== '$c '==='; git show --stat --format=fuller --summary $c; echo; doneDetermining changelog entries
I need to find missing changelog entries and possibly add them directly. It looks like there might be several commits without entries, like handling missing session cwd and resource collision precedence. I wonder if I should include entries for example changes that are essential for users or skip those that are just doc-only. There’s also a cross-package duplication to consider. I should inspect existing entries to see if they indirectly cover the issues, but I may need to read through the whole coding-agent changelog for context.
>git show --stat --format=medium 080af6fc && printf '\n---PATCH 080af6fc---\n' && git show --unified=40 --format=medium -- packages/coding-agent/src/core/session-cwd.ts packages/coding-agent/src/main.ts packages/coding-agent/src/modes/interactive/interactive-mode.ts 080af6fc && printf '\n---PATCH a7acef92---\n' && git show --unified=40 --format=medium a7acef92 -- packages/coding-agent/src/core/package-manager.ts packages/coding-agent/src/core/resource-loader.tsInspecting patch issue
I realized that the patch for 080 isn't showing due to a command mistake on my part. I think I should take a closer look at the tests and maybe summarize the results. It might be helpful to check specific files, as I suspect the command ordering could be wrong. I definitely need to handle this properly to ensure everything goes smoothly! Let's figure out the best approach together.
>echo '---080 session-cwd.ts---' && git show 080af6fc:packages/coding-agent/src/core/session-cwd.ts && printf '\n---080 main diff---\n' && git diff 080af6fc^ 080af6fc -- packages/coding-agent/src/main.ts packages/coding-agent/src/core/session-manager.ts packages/coding-agent/src/core/agent-session-runtime.ts packages/coding-agent/src/modes/interactive/interactive-mode.tsOrganizing features and reports
I'm focusing on some specifics: I've got the codes to manage, like 52d, 127, 71, etc., and I need to handle the missing elements, like 080 and a7. I should skip the docs-only for now since they're in the changelog. I need to create a report about that. I also need to insert a "New Features" section at the beginning of the "Unreleased" part in the coding agent and suggest the top features before I start writing them.
Considering Git Documentation
I should mention that a document-only entry seems extraneous. Maybe the user is asking to audit all commits rather than modify extras. Do I need to use git diff? Perhaps not, given that it's just documentation. I might gather the git log without the changelog instead. That could be enough for what I need. It might also be a good idea to verify this by checking the top of the file.
Evaluating new features section
It looks like all commits since the last release are just fixes and no new features, so I’m pondering whether to add a section for new features. The instructions say to include one after the changelog, but I think I could mention that there aren't any user-facing new features since v0.65.0. Maybe I could propose an empty placeholder for that section and confirm with the user if they’d like it. It might be good to clarify that nothing's been added yet.
Identifying missing commit entries
I need to address some commits that seem to have missing entries, like 080af6fc, a7acef92, and 6044cabb, which involve duplication. I should mention that the existing doc-only entry, 0c98d5a5, should be skipped since it’s already there. Other commits like 02c2, 1a6, fbd35, and 84d are also potential skips. It seems 6044 has already been covered in the AI context, so I’m trying to clarify what to do with these.
Yes.
Audit done for commits since v0.65.0.
Updated:
packages/coding-agent/CHANGELOG.mdAdded missing entries:
080af6fc fix(coding-agent): handle missing session cwda7acef92 fix(coding-agent): resource collision precedence...6044cabb fix(ai): preserve cache_write_tokens... into packages/coding-agent/CHANGELOG.mdReport:
Missing changelog entries
080af6fc fix(coding-agent): handle missing session cwda7acef92 fix(coding-agent): resource collision precedence, user/project skills override package skillsNeeded cross-package duplication
6044cabb fix(ai): preserve cache_write_tokens in completions stream usage closes #2802
packages/ai/CHANGELOG.mdpackages/coding-agent/CHANGELOG.mdAlready covered
52d16d5a bash output temp-file persistence127547f2 preserve JSON mode for piped stdin71e44369 git/npm extension path handling5e5eeb96 async fs.watch errors72a43dc0 RpcClient stderr forwardingSkipped correctly
1a6a58eb contributor list only02c2a3e5 example-only shell script fixfbd35a46 test rename84d13406 release housekeepingEntry that should probably be skipped
0c98d5a5 fix(coding-agent): remove stale /exit docs closes #2850
packages/coding-agent/CHANGELOG.md has an entry for it### New Features section proposal for packages/coding-agent/CHANGELOG.md
v0.65.0If you still want the section inserted now, I recommend one of these:
### New Features under ## [Unreleased]My recommendation is 2. If you want 1, I can add the empty section.
no need for features, wrap this up
Done.
Changed:
packages/coding-agent/CHANGELOG.mdSummary:
ai cache token accounting fix into coding-agent/exit changelog entry as-is### New FeaturesAnything else on this audit?
commit and push, then do a patch release
>git status --shortCommitting changes
I need to commit our file with a message like "docs(coding-agent): fill missing changelog entries." There doesn’t seem to be any issues, so I’m not closing anything. I should commit and push this. But wait, I need to confirm if I'm on the current branch, possibly the main branch? Let me check and make sure everything is in order before I proceed!
>git branch --show-current && git add packages/coding-agent/CHANGELOG.md && git commit -m "docs(coding-agent): audit unreleased changelog entries" && git push>git pull --rebase && git pushRunning release script
I’m looking at the patch release and it seems like I need to run the release script. I expect it might take a little while to complete, so I want to keep that in mind. It’s important to ensure everything goes smoothly during this process. I’m reminding myself to be patient and double-check everything afterward to confirm that the release was successful. I’ll dive into that now!
>npm run release:patchConsidering commit hashes
I need to make sure I mention the commit hashes and possibly a release tag in the final version. It's important to keep things concise while still providing the necessary details. I'm thinking about how best to present this information clearly. It seems like including both would give a complete overview without overwhelming anyone with too much detail. I'll finalize the wording to ensure it's precise and easy to understand!
Done.
Committed and pushed:
db31c16b docs(coding-agent): audit unreleased changelog entriesPatch release:
v0.65.1mainv0.65.1The release script also added fresh [Unreleased] sections for the next cycle and committed that as part of the release flow.
git tag --sort=-version:refname | head -1git log <tag>..HEAD --oneline