fix(changesets): rename stale @cipherstash/cli key to stash#404
Conversation
The CLI package was renamed from `@cipherstash/cli` to `stash` in packages/cli/package.json, but two changesets still referenced the old name. The changesets/version action on main fails with: Found changeset cli-runner-aware-help-banners for package @cipherstash/cli which is not in the workspace Updates both frontmatter keys to the current package name. Body copy that mentions `@cipherstash/cli` historically is left intact — changesets only validates the YAML frontmatter package keys.
|
| Name | Type |
|---|---|
| stash | Patch |
| @cipherstash/wizard | Patch |
| @cipherstash/protect | Patch |
| @cipherstash/drizzle | Patch |
| @cipherstash/e2e | Patch |
| @cipherstash/protect-dynamodb | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 47 minutes and 27 seconds.Comment |
The ciphertext-free approach was non-functional: encryptQuery can't mint a
scalar/ordering query term against a ste_vec (JSON) column, so the value call
threw "Index type not configured" (caught by CI's live integration job).
Verified via FFI probes: the stored ste_vec entry at the JSONPath selector
carries c + op (ordering) / hm (equality), and encryptQuery('$.path') returns
the selector that matches it. So the RHS is a STORAGE encryption of {path: value}
whose entry is extracted with jsonb_path_query_first and compared entry-vs-entry
(eq_term/ord_term read only hm/op). Ciphertext-free ordering needs a protect-ffi
change (cipherstash/protectjs-ffi#137); until then the value's ciphertext is in
the WHERE clause — documented inline.
Also from the code review: use Promise.all for the two independent encrypts;
throw (not silently mis-bind) if the selector term isn't a bare string; fix path
normalization (leading $/.) and reject the empty/root path; drop the fragile
JS-type→query-domain inference entirely.
Refs #623 · protect-ffi gap cipherstash/protectjs-ffi#137 · EQL operator #404
Claude-Session: https://claude.ai/code/session_01MxTTPaPP16m6br7Hoab94w
1 participant
Summary
@cipherstash/cli→stashinpackages/cli/package.json, but two changesets onmainstill reference the old name.main:@cipherstash/clihistorically is left intact — changesets only validates frontmatter.Files touched:
.changeset/cli-runner-aware-help-banners.md.changeset/package-manager-aware-output.mdTest plan
🤖 Generated with Claude Code