Skip to content

SK-3262: bump skyvault to 2.2.0 for public release (Detect V2) - #294

Open
saileshwar-skyflow wants to merge 1 commit into
mainfrom
saileshwar/SK-3262-public-release-skyvault
Open

saileshwar-skyflow wants to merge 1 commit into
mainfrom
saileshwar/SK-3262-public-release-skyvault

Conversation

@saileshwar-skyflow

Copy link
Copy Markdown
Collaborator

What

Bumps the skyvault SDK (dist skyflow) from 2.1.3 → 2.2.0 for the public PyPI release that includes Detect V2.

  • skyvault/setup.py → current_version = '2.2.0'
  • skyvault/skyflow/utils/_version.py → SDK_VERSION = '2.2.0'

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

Why

Detect V2 (deidentify/reidentify string+file, getRun, checkGuardrails) landed on main via #292 (shared common/, re-exported from skyvault/skyflow/vault/detect) after the 2.1.3 release, which did not ship detect. 2.2.0 is a minor bump for the new feature.

Verified (already on main, no changes needed here)

  • README: detect documented, split enums (DeidentifyFileDataFormat/ReidentifyFileDataFormat), no leftover FileDataFormat.
  • samples/detect_api/: all 6 detect samples present and import cleanly against the built SDK.
  • api-report: matches the flowvault detect contract (24 DeidentifyFileDataFormat, 9 ReidentifyFileDataFormat).
  • e2e: python skyvault detect suite 142/142 green against a 2.2.0-equivalent build (SK-3262 branch in sdk-integration-tests).

Release steps after merge

  1. Merge this PR to main.
  2. Create a GitHub Release with tag 2.2.0 targeting main.
  3. release.yml publishes skyflow==2.2.0 to PyPI.

Scope

Version-only change in this PR — no functional diff.

🤖 Generated with Claude Code

Detect V2 landed on main (shared common/, re-exported from skyvault) after
the 2.1.3 release, which did not include it. Bump the skyvault SDK (dist
skyflow) to 2.2.0 -- a minor release for the new detect feature. Both
setup.py and _version.py are patched by bump_version.sh and must match.

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

Copy link
Copy Markdown

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

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