chore: release 0.39.39 (Codex fork overcount fix #75)#79
Merged
Conversation
Ships the issue #75 Codex subagent fork-history fix that is already on main: - #77 parser fix (exclude replayed fork parent history from token accounting) - #78 one-time rebuild migration for already-inflated Codex aggregates The version bump is what lets npm-publish.yml actually publish main (the job skips while the package.json version already exists on npm). Required so the dashboard LaunchAgent and `npx @ipv9/tokentracker-cli sync` pick up the fixed parser + migration instead of the still-inflated 0.39.38. Co-authored-by: itarun.p <itarun.p@somapait.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the package version to 0.39.39 so
npm-publish.ymlpublishes main, which now carries the issue #75 fix (parser #77 + rebuild migration #78). Without the bump the publish job self-skips and users stay on the inflated 0.39.38.npm run ci:localgreen (765/765)serve --syncuses the fixed parser (the old one re-inflates on re-parse)Refs #75