Skip to content

SK-3206: bump flowvault to 1.1.0 for public release - #293

Merged
saileshwar-skyflow merged 1 commit into
mainfrom
saileshwar/SK-3206-public-release-flowvault
Nov 11, 2026
Merged

saileshwar-skyflow merged 1 commit into
mainfrom
saileshwar/SK-3206-public-release-flowvault

Conversation

@saileshwar-skyflow

Copy link
Copy Markdown
Collaborator

What

Bumps the flowvault SDK (skyflow-flowvault-python) version from 1.0.1.dev0+18a5d86 → 1.1.0 for the public PyPI release.

  • flowvault/setup.py → current_version = '1.1.0'
  • flowvault/skyflow/utils/_version.py → SDK_VERSION = '1.1.0'

Both files are patched by bump_version.sh and must stay in lockstep.

Why

1.1.0 is the first public release carrying Detect V2 + the new flowvault interfaces (landed via #292). Pre-setting the version on main means the release workflow's bump_version.sh produces no diff, so its "Commit changes" step no-ops and never pushes to protected main.

Release steps after merge

  1. Merge this PR to main.
  2. Create a GitHub Release with tag flowvault/v1.1.0 targeting main.
  3. release.yml publishes skyflow-flowvault-python==1.1.0 to PyPI.

Scope

Version-only change — no functional diff.

🤖 Generated with Claude Code

Set current_version (setup.py) and SDK_VERSION (_version.py) to 1.1.0.
The public release is cut from this version so CI's version-bump step
is a no-op (no push to the protected main branch).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

✅ Gitleaks Findings: No secrets detected. Safe to proceed!

@github-actions

Copy link
Copy Markdown

✅ Gitleaks Findings: No secrets detected. Safe to proceed!

@saileshwar-skyflow
saileshwar-skyflow merged commit 3737a0e into main Nov 11, 2026
26 checks passed
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.

3 participants