Skip to content

SK-3118: Fix root README for the unary-only FlowVault SDK - #279

Merged
saileshwar-skyflow merged 2 commits into
mainfrom
docs/root-readme-flowvault-unary
Sep 16, 2026
Merged

saileshwar-skyflow merged 2 commits into
mainfrom
docs/root-readme-flowvault-unary

Conversation

@saileshwar-skyflow

Copy link
Copy Markdown
Collaborator

Summary

The repo landing page (README.md) was out of date after the FlowVault SDK went unary-only. This corrects it and aligns its structure with the skyflow-java root README (same monorepo-index shape).

Fixes

  • Import name: flowvault row said import skyflow_flowvault → corrected to import skyflow (the package's top-level module is skyflow).
  • Bulk removed: "Flow DB (v1.x) — high-throughput bulk + unary vault operations" → "FlowVault (v1.x) — unary vault operations (insert, get, update, delete, detokenize)".
  • Naming: "Flow DB" → "FlowVault" throughout (per the Python docs convention).
  • Coexistence note: clarified that both artifacts install under the same top-level skyflow import and can't share one environment.

Structure (aligned to Java)

  • Kept "Which package do I want?" and "Repository layout".
  • Replaced "Resources" with a Documentation section and added a Reporting a Vulnerability section (security@skyflow.com), matching the Java root README.

All linked paths verified to exist (docs/migrate_to_v2.md, CHANGELOG.md, both SDK READMEs and samples/ dirs).

Note: the Java root README still uses the "Flow DB" product name; this PR uses "FlowVault" to match the Python docs. If you'd rather keep "Flow DB" for cross-repo consistency, it's a one-line change — say the word.

🤖 Generated with Claude Code

saileshwar-skyflow and others added 2 commits September 16, 2026 15:14
The repo landing page was stale: it showed flowvault importing as
`skyflow_flowvault` (it imports as `skyflow`), described it as
"high-throughput bulk + unary" (bulk has been removed — it is unary only), and
used the retired "Flow DB" name. Correct the import name and description, rename
Flow DB -> FlowVault, and align the page structure with the Java repo's root
README (add Documentation and Reporting a Vulnerability sections; note that both
artifacts share the `skyflow` import and can't coexist in one environment).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Follow the skyflow-java root README structure: title + intro + CI/release/license
badges, a "Which package do I want?" table (Package / Artifact / README /
Vault Type / Version line), the independent-versioning note, repository layout,
Documentation, and Reporting a Vulnerability. Vault types are named SkyVault and
FlowVault. Also keeps the Python-specific note that both artifacts share the
`skyflow` import and must be installed one per environment.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@saileshwar-skyflow
saileshwar-skyflow merged commit 2d8350f into main Sep 16, 2026
8 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