Skip to content

chore(release): bump workspace to 0.15.1#173

Merged
risjai merged 1 commit into
masterfrom
chore/bump-v0.15.1
May 22, 2026
Merged

chore(release): bump workspace to 0.15.1#173
risjai merged 1 commit into
masterfrom
chore/bump-v0.15.1

Conversation

@risjai

@risjai risjai commented May 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Bumps Rust workspace + binary version trackers from 0.15.00.15.1 (5 files per CLAUDE.md Track 1).
  • Bumps python-mcp pip package version from 0.13.100.13.11.
  • No source changes — mechanical version bumps only.

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.yml triggers on push to master + Cargo.toml change AND that the new version isn't already tagged — but since Cargo.toml still said 0.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_id in the dispatch body, but rewind-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.00.15.1
  • Cargo.lock: 10 workspace crates auto-updated to 0.15.1 via cargo update
  • python/rewind_cli.py CLI_VERSION: 0.15.00.15.1
  • python-mcp/rewind_mcp_cli.py CLI_VERSION: 0.15.00.15.1
  • python-mcp/pyproject.toml version: 0.13.100.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)
  • Diff confirmed to be only version-string updates

Post-merge

  1. release.yml should detect the Cargo.toml change + new version, build the linux-x86_64 tarball, and create the v0.15.1 GitHub Release automatically.
  2. After the GitHub Release exists, the artifactory tarball will be available at rewind-v0.15.1-linux-x86_64.tar.gz.
  3. Consumers (e.g. Dockerfile.rewind-server in downstream apps) update their tarball URL + SHA256 in a follow-up.
  4. python-mcp/pyproject.toml changed → run ./scripts/publish-mcp-pypi.sh from python-mcp/ to publish rewind-mcp==0.13.11 to PyPI.

Test plan

  • CI clippy + tests pass on this PR.
  • After merge: confirm release.yml created v0.15.1 tag + GitHub Release with the tarball asset.
  • After tarball is available: deploy with the new sidecar version and verify dashboard "Run replay" succeeds (no longer 400).

🤖 Generated with Claude Code

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>
@vercel

vercel Bot commented May 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
rewind Ready Ready Preview, Comment May 22, 2026 5:35am

@risjai
risjai merged commit 1137bbc into master May 22, 2026
7 checks passed
@risjai
risjai deleted the chore/bump-v0.15.1 branch May 22, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant