Bump version to 0.7.0 - #773
Merged
Merged
Conversation
0.7.0 is a minor bump rather than a patch because it adds a new data model and new user-facing surfaces, not just fixes. Sessions now carry repo context and developer identity, the session-to-commit join lands alongside the shipped analyzer, git hooks write commit trailers and notes, and `tj init` gains the flags that wire all of it up including the optional Cloud bridge. All four lockstep version files move together: pyproject.toml, sdk-ts/package.json, npm-wrapper/package.json and plugin/.claude-plugin/plugin.json. CI's version-lockstep job compares the last of those against pyproject.toml. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
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
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.
Cuts OSS 0.7.0. A minor bump rather than a patch: this release adds a new data model and new user-facing commands, not just fixes.
Summary
Four lockstep version files move from 0.6.12 to 0.7.0:
pyproject.toml,sdk-ts/package.json,npm-wrapper/package.jsonandplugin/.claude-plugin/plugin.json. The last of those is checked againstpyproject.tomlby CI'sversion-lockstepjob, so a drift fails here rather than shipping a stale marketplace entry.What is in 0.7.0
The ledger. Sessions now record the repository they ran in and the developer identity behind them. A new join links a session to the commits it produced, each match carrying a confidence level so a guess is never presented as a fact. On top of that sits the
shippedanalyzer, which separates work that reached the default branch from work that did not, and surfaces unshipped burn, rework and loop cost through the CLI, the REST API and the Lens.First run and onboarding.
tj initis the primary entry point and gains--hooks,--notes,--enforce,--cloud,--organd--add-project. Aprepare-commit-msghook writes the session trailer and apost-commithook writes the git note, both under managed blocks that uninstall cleanly.tj commit-notewrites one by hand.The Cloud bridge, off by default. A
[cloud]config block and a daemon-side forwarder can push session summaries to TokenJam Cloud for teams that want them.tj statusandtj doctorboth report its state. It stays off until explicitly enabled, and it was developed against a recorded fake receiver so the tests never touch a live endpoint.Correctness. Repo context is refilled on sessions ingested without it. The matcher runs on the daemon when the CLI cannot. Branch endpoints are picked by timestamp rather than by remote query string (#762). An inherited session trailer now ranks below the tool span that actually ran the commit. The Lens hero CTA resolves to a surface that renders the analyzer it names instead of a retired route.
Contributors
Every commit in this range is authored by Anil Murty. No external contributions to credit in these notes; PR #750 from a first-time contributor is still open and deliberately deferred to a later release rather than rushed into this one.
Gating
Do NOT merge this until both release gates clear:
Tagging fires irreversible public publishes to PyPI and npm.
What's NOT in this PR
No code changes and no release notes file. This is the version bump alone. Documentation for the new surfaces is in a separate PR so a docs review cannot hold up the tag.
🤖 Generated with Claude Code