Repository navigation
chore: bump version to 2.1.1 - #26
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MSBPh6sGS1DeMA7GEabXAz
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (8)
Included review availability: 1 review is currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. 📝 WalkthroughWalkthroughUpdated all listed VegaFusion package versions from 2.1.0 to 2.1.1. Updated internal Rust dependency pins in the core, Python, runtime, server, and WASM packages. Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This change updates the project version to 2.1.1 without altering product behavior, so no actionable merge-blocking risk remains beyond normal release checks. 🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
Comment |
Version bump to
2.1.1in preparation for the next release, generated withautomation/bump_version.py(pixi run bump-version 2.1.1) pluscargo update --workspaceto refreshCargo.lock.Only version strings change — the diff is line-for-line the same shape as the previous bump (4c526a4).
Changes since v2.1.0:
After merge, publish a GitHub Release tagged
v2.1.1on the merge commit — that triggers.github/workflows/release.yml, which builds all-platform wheels, attaches them to the release, and publishesdeepnote-vegafusion2.1.1 to PyPI.🤖 Generated with Claude Code
https://claude.ai/code/session_01MSBPh6sGS1DeMA7GEabXAz
Summary by CodeRabbit