chore(release): bump workspace to 0.15.1#173
Merged
Merged
Conversation
PR #167 ("fix(replay): dispatch source_timeline_id so handler reads edited steps") merged to master without bumping the workspace version, so the release.yml pipeline saw v0.15.0 already-tagged and skipped the auto-release. The fix shipped to master but never made it into a binary tarball, leaving deployed v0.15.0 sidecars unable to drive replay against rewind-agent>=0.16.0 SDKs (the SDK requires source_timeline_id; the v0.15.0 dispatcher doesn't send it → 400 on every dashboard "Run replay"). This bumps Track 1 (Rust workspace + binary trackers) per CLAUDE.md: - Cargo.toml: 0.15.0 → 0.15.1 - Cargo.lock: all 10 workspace crates updated to 0.15.1 - python/rewind_cli.py CLI_VERSION: 0.15.0 → 0.15.1 - python-mcp/rewind_mcp_cli.py CLI_VERSION: 0.15.0 → 0.15.1 - python-mcp/pyproject.toml version: 0.13.10 → 0.13.11 (independent pip track for the MCP wrapper package) Verified locally: - cargo check --workspace --all-targets: clean - cargo clippy -- -D warnings (CI mode): clean - diff is mechanical version bumps only; no source changes Post-merge: - release.yml will detect Cargo.toml change + new version → tag v0.15.1 and publish the linux-x86_64 tarball as a GitHub Release - Operators bump Dockerfile.rewind-server to point at the new tarball + SHA256 (separate follow-up in consuming repos) - python-mcp/pyproject.toml change → run ./scripts/publish-mcp-pypi.sh Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
0.15.0→0.15.1(5 files per CLAUDE.md Track 1).python-mcppip package version from0.13.10→0.13.11.Why
PR #167 (
fix(replay): dispatch source_timeline_id so handler reads edited steps) merged to master on 2026-05-21 without bumping the workspace version.release.ymltriggers onpush to master+Cargo.tomlchange AND that the new version isn't already tagged — but sinceCargo.tomlstill said0.15.0(the existing tag), the pipeline ran but skipped the release.Net effect: the dispatch fix is in master but no binary tarball was published with it. Deployed v0.15.0 sidecars don't include
source_timeline_idin the dispatch body, butrewind-agent==0.16.0+requires it as a mandatory field — every dashboard "Run replay" →400 invalid dispatch body: 'source_timeline_id'.Files changed
Cargo.toml:0.15.0→0.15.1Cargo.lock: 10 workspace crates auto-updated to 0.15.1 viacargo updatepython/rewind_cli.pyCLI_VERSION:0.15.0→0.15.1python-mcp/rewind_mcp_cli.pyCLI_VERSION:0.15.0→0.15.1python-mcp/pyproject.tomlversion:0.13.10→0.13.11(independent pip track for the MCP wrapper)Verification
cargo check --workspace --all-targets: clean (exit 0)cargo clippy -- -D warnings(CI mode): clean (exit 0)Post-merge
release.ymlshould detect theCargo.tomlchange + new version, build the linux-x86_64 tarball, and create the v0.15.1 GitHub Release automatically.rewind-v0.15.1-linux-x86_64.tar.gz.Dockerfile.rewind-serverin downstream apps) update their tarball URL + SHA256 in a follow-up.python-mcp/pyproject.tomlchanged → run./scripts/publish-mcp-pypi.shfrompython-mcp/to publishrewind-mcp==0.13.11to PyPI.Test plan
v0.15.1tag + GitHub Release with the tarball asset.🤖 Generated with Claude Code