From 8dc2ebe5328e6280ed46558013f573fac2a32180 Mon Sep 17 00:00:00 2001 From: Toby Hede Date: Wed, 19 Aug 2026 11:47:49 +1000 Subject: [PATCH 1/3] docs(release): explain the 2.0.0 alignment, the FFI repository change, and stop the CHANGELOG preamble shipping MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Three defects found auditing the Version Packages PR (#859), all in what consumers will read on npm. **Five packages ship a major with nothing to show for it.** `stash`, `@cipherstash/stack`, `stack-drizzle`, `stack-supabase` and `wizard` go 1.0.0 → 2.0.0 carrying only Minor and Patch entries — `wizard` carrying none at all, a heading followed by two blank lines. The one real breaking change is in `stack-prisma` (Prisma Next 0.17), and the other five inherit its number through the Changesets `fixed` group. Nothing in 485 lines of release notes said so, so a `stack-drizzle` user would have gone looking for a migration guide that does not exist. A changeset now says it in the changelog itself, where they will actually look, and explains why the packages are versioned together: `stash` embeds the versions it installs, so a package shipping alone would leave the CLI recommending versions that no longer match what is published. **The six platform packages had no entry at all.** 0.32.0 is their first release published from `cipherstash/stack` rather than `cipherstash/protectjs-ffi`, and the attested provenance repository changes with it — a verification policy that pins the source repository rejects 0.32.0 until updated. That was invisible to the person it affects, who reads the platform package they install rather than the wrapper. **The CHANGELOG preamble was publishing as release notes.** `changeset version` splices each release directly after the `# Changelog` line, so the hand-written preamble beneath it landed inside the newest section, under its heading: thirteen lines of 0.32.0 ending with "Write a changeset, not a section here" — an instruction to contributors, shipped to npm. It moves below the generated entries, where it explains the file's two halves and cannot be swept again, with a comment recording why nothing may sit above the first release heading. Verified by running `changeset version` and rolling it back: the seven FFI packages still land on 0.32.0 and the six Stack packages on 2.0.0 — these changesets add prose, not version bumps — `wizard`'s and each platform package's entries are no longer empty, and no preamble text remains inside 0.32.0. --- ...platform-packages-publishing-repository.md | 30 +++++++++++++++ .changeset/stack-2-0-0-version-alignment.md | 32 ++++++++++++++++ packages/protect-ffi/CHANGELOG.md | 37 ++++++++++++------- 3 files changed, 86 insertions(+), 13 deletions(-) create mode 100644 .changeset/ffi-platform-packages-publishing-repository.md create mode 100644 .changeset/stack-2-0-0-version-alignment.md diff --git a/.changeset/ffi-platform-packages-publishing-repository.md b/.changeset/ffi-platform-packages-publishing-repository.md new file mode 100644 index 000000000..a95df898e --- /dev/null +++ b/.changeset/ffi-platform-packages-publishing-repository.md @@ -0,0 +1,30 @@ +--- +'@cipherstash/protect-ffi-darwin-x64': patch +'@cipherstash/protect-ffi-darwin-arm64': patch +'@cipherstash/protect-ffi-win32-x64-msvc': patch +'@cipherstash/protect-ffi-linux-x64-gnu': patch +'@cipherstash/protect-ffi-linux-arm64-gnu': patch +'@cipherstash/protect-ffi-linux-x64-musl': patch +--- + +**This is the first release of these packages published from +`cipherstash/stack`.** Every version up to and including 0.31.0 was published +from `cipherstash/protectjs-ffi`, which is now archived. + +If you verify npm provenance, the attested source repository changes with this +release: + +``` +0.31.0 github.com/cipherstash/protectjs-ffi .github/workflows/release.yml +0.32.0 github.com/cipherstash/stack .github/workflows/release.yml +``` + +A verification policy that pins the source repository will reject 0.32.0 until +it is updated. The packages, their contents and their maintainers are otherwise +unchanged — the Rust source moved into the monorepo at +`packages/protect-ffi/crates/protect-ffi`, and each platform package's +`repository.url` and `repository.directory` now point there. + +The binaries themselves also differ from 0.31.0 in one user-visible way: the +Rust core's `InvariantViolation` message asks the reader to file an issue, and +the repository it names has moved with the rest. diff --git a/.changeset/stack-2-0-0-version-alignment.md b/.changeset/stack-2-0-0-version-alignment.md new file mode 100644 index 000000000..c225862f1 --- /dev/null +++ b/.changeset/stack-2-0-0-version-alignment.md @@ -0,0 +1,32 @@ +--- +'stash': major +'@cipherstash/stack': major +'@cipherstash/stack-drizzle': major +'@cipherstash/stack-supabase': major +'@cipherstash/wizard': major +--- + +**No breaking changes in this package.** Upgrading from 1.x to 2.0.0 needs no +code changes, and there is no migration guide to look for. + +The major version comes from `@cipherstash/stack-prisma`, which does have a +breaking change this release — it moves to Prisma Next 0.17, and its own +changelog carries the upgrade steps. These six packages share a single version +line, so a major in any one of them takes all six to the same number: + +- `stash` +- `@cipherstash/stack` +- `@cipherstash/stack-drizzle` +- `@cipherstash/stack-supabase` +- `@cipherstash/stack-prisma` +- `@cipherstash/wizard` + +They are versioned together on purpose. `stash init` pins the versions of the +packages it installs, and the CLI embeds that map at build time — so if one +package could ship without the others, the CLI would start recommending +versions that no longer match what is published, and warn about a skew it had +itself created. + +**If you do not use `@cipherstash/stack-prisma`, this release is additive.** +Read your package's own Minor and Patch entries below for what actually changed +in it. diff --git a/packages/protect-ffi/CHANGELOG.md b/packages/protect-ffi/CHANGELOG.md index 11be50ed5..9956ed1ba 100644 --- a/packages/protect-ffi/CHANGELOG.md +++ b/packages/protect-ffi/CHANGELOG.md @@ -1,18 +1,29 @@ # Changelog -All notable changes to this project are documented in this file. - -The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), -and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). -While the project is pre-1.0, breaking changes are released as minor version -bumps and called out under a `Breaking` heading — an addition to the standard -Keep a Changelog categories (Added/Changed/Deprecated/Removed/Fixed/Security). - -Entries from 0.31.0 down were written by hand under an `[Unreleased]` heading -and promoted on release by an npm `version` lifecycle hook. That hook is gone: -since this package moved into the `cipherstash/stack` monorepo, Changesets -generates each entry from the changesets in a release, and appends it below in -its own format. Write a changeset, not a section here. +## About the entries below 0.31.0 + +Everything from `[0.31.0]` down was written by hand, under an `[Unreleased]` +heading that an npm `version` lifecycle hook promoted on release. Those entries +follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), with a +`Breaking` heading added for the pre-1.0 convention of shipping breaking changes +as minor bumps. + +That hook is gone. Since this package moved into the `cipherstash/stack` +monorepo, Changesets generates every entry above this heading from the +changesets in a release, in its own format. + + ## [0.31.0] - 2026-07-27 From ba3830f4122f3477c90efd40b7d18c1ebbb5549a Mon Sep 17 00:00:00 2001 From: Toby Hede Date: Wed, 19 Aug 2026 12:25:55 +1000 Subject: [PATCH 2/3] fix(release): correct the alignment note's false claims, and make these notes reach npm MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Review findings on the previous commit, all in text it would have published. **"No breaking changes in this package" was false for two of the five.** The same 2.0.0 ships `@cipherstash/stack`'s hex-only `clientKey` — a base64 value is now rejected at client construction — and `stash`'s removal of `stash eql validate --exclude-operator-family`, plus two checks that no longer exit 1. Both are recorded at patch and minor respectively, which is a deliberate maintainer call (#874: an undocumented decoder tolerance is not a contract break, and should not by itself take five packages to 2.0.0). That call is not reversed here — but a reader following "needs no code changes" into a failed client construction is not served by it either, so the note now names both, says where they are, and confines the drop-in claim to users of neither. **"cipherstash/protectjs-ffi, which is now archived" was false.** The repository is live; archiving is the last step of the cutover, after this release. Stated as future, matching the sibling changeset that already had it right. **The notes did not reach the packages they were written for.** `CHANGELOG.md` was absent from `files` in `stack-drizzle`, `stack-supabase`, `stack-prisma`, the protect-ffi wrapper and all six platform packages — so the provenance note aimed at "the package a checker actually installs" shipped nowhere near it, and "its own changelog carries the upgrade steps" pointed a Prisma user at a file absent from their install. Added to all ten. Verified by `npm pack --dry-run`: `stack-drizzle` now carries its 34.3kB CHANGELOG. The platform packages' copies are generated by `changeset version`, and `_build-ffi-artifacts.yml` packs from `changeset-release/main` after that runs, so the file exists at pack time. **`repository.directory` does not point at the crate.** It points at each platform's own stub under `packages/protect-ffi/platforms/`; only `repository.url` moved to `cipherstash/stack`. **The moved CHANGELOG section contradicted itself.** The heading excluded 0.31.0 while its first line included it, and its comment stated a rule stricter than the real invariant — the constraint is headingless prose, since a heading terminates the preceding section. Both corrected, and the comment's claim about npm, false when written, is true now that the file is in `files`. Versions are unchanged: seven FFI packages at minor, six Stack packages at major. `test:scripts` 416 passing; all ten manifests parse. --- ...platform-packages-publishing-repository.md | 18 +++++--- .changeset/ship-changelogs-in-tarballs.md | 12 ++++++ .changeset/stack-2-0-0-version-alignment.md | 43 +++++++++++++------ packages/protect-ffi/CHANGELOG.md | 27 ++++++------ packages/protect-ffi/package.json | 3 +- .../platforms/darwin-arm64/package.json | 3 +- .../platforms/darwin-x64/package.json | 3 +- .../platforms/linux-arm64-gnu/package.json | 3 +- .../platforms/linux-x64-gnu/package.json | 3 +- .../platforms/linux-x64-musl/package.json | 3 +- .../platforms/win32-x64-msvc/package.json | 3 +- packages/stack-drizzle/package.json | 3 +- packages/stack-prisma/package.json | 3 +- packages/stack-supabase/package.json | 3 +- 14 files changed, 87 insertions(+), 43 deletions(-) create mode 100644 .changeset/ship-changelogs-in-tarballs.md diff --git a/.changeset/ffi-platform-packages-publishing-repository.md b/.changeset/ffi-platform-packages-publishing-repository.md index a95df898e..fd6ebddc9 100644 --- a/.changeset/ffi-platform-packages-publishing-repository.md +++ b/.changeset/ffi-platform-packages-publishing-repository.md @@ -9,7 +9,7 @@ **This is the first release of these packages published from `cipherstash/stack`.** Every version up to and including 0.31.0 was published -from `cipherstash/protectjs-ffi`, which is now archived. +from `cipherstash/protectjs-ffi`, which is archived once this release is out. If you verify npm provenance, the attested source repository changes with this release: @@ -21,10 +21,14 @@ release: A verification policy that pins the source repository will reject 0.32.0 until it is updated. The packages, their contents and their maintainers are otherwise -unchanged — the Rust source moved into the monorepo at -`packages/protect-ffi/crates/protect-ffi`, and each platform package's -`repository.url` and `repository.directory` now point there. +unchanged: the Rust source moved into the monorepo at +`packages/protect-ffi/crates/protect-ffi`, and each of these packages' +`repository.url` now names `cipherstash/stack`, with `repository.directory` +pointing at its own stub under `packages/protect-ffi/platforms/`. -The binaries themselves also differ from 0.31.0 in one user-visible way: the -Rust core's `InvariantViolation` message asks the reader to file an issue, and -the repository it names has moved with the rest. +`CHANGELOG.md` is also added to each package's published files, so this note and +later ones are readable in the package you install rather than only on GitHub. + +The binaries themselves differ from 0.31.0 in one user-visible way: the Rust +core's `InvariantViolation` message asks the reader to file an issue, and the +repository it names has moved with the rest. diff --git a/.changeset/ship-changelogs-in-tarballs.md b/.changeset/ship-changelogs-in-tarballs.md new file mode 100644 index 000000000..5e574d85e --- /dev/null +++ b/.changeset/ship-changelogs-in-tarballs.md @@ -0,0 +1,12 @@ +--- +'@cipherstash/stack-prisma': patch +'@cipherstash/protect-ffi': patch +--- + +Ship `CHANGELOG.md` inside the published tarball. It was missing from `files`, +so the release notes for these packages were readable on GitHub and on the npm +web page but not in the package you actually install — which is the copy you +have when something breaks offline, or when the repository has moved. + +`@cipherstash/stack-drizzle` and `@cipherstash/stack-supabase` gain it in the +same release, as do the six `@cipherstash/protect-ffi-` packages. diff --git a/.changeset/stack-2-0-0-version-alignment.md b/.changeset/stack-2-0-0-version-alignment.md index c225862f1..373f6108a 100644 --- a/.changeset/stack-2-0-0-version-alignment.md +++ b/.changeset/stack-2-0-0-version-alignment.md @@ -6,13 +6,11 @@ '@cipherstash/wizard': major --- -**No breaking changes in this package.** Upgrading from 1.x to 2.0.0 needs no -code changes, and there is no migration guide to look for. - -The major version comes from `@cipherstash/stack-prisma`, which does have a -breaking change this release — it moves to Prisma Next 0.17, and its own -changelog carries the upgrade steps. These six packages share a single version -line, so a major in any one of them takes all six to the same number: +**Why this package went to 2.0.0.** The major version number comes from +`@cipherstash/stack-prisma`, which moves to Prisma Next 0.17 — a breaking change +for its consumers, with the upgrade steps in its own Major Changes entry. These +six packages share one version line, so a major in any of them takes all six to +the same number: - `stash` - `@cipherstash/stack` @@ -22,11 +20,28 @@ line, so a major in any one of them takes all six to the same number: - `@cipherstash/wizard` They are versioned together on purpose. `stash init` pins the versions of the -packages it installs, and the CLI embeds that map at build time — so if one -package could ship without the others, the CLI would start recommending -versions that no longer match what is published, and warn about a skew it had -itself created. +packages it installs and the CLI embeds that map at build time, so a package +shipping alone would leave the CLI recommending versions that no longer match +what is published, and warning about a skew it had itself created. + +**This does not mean every package in the release is drop-in.** The version +number is shared; the changes are not. Two entries below need action from some +users, and neither is filed under Major Changes — they are recorded at the level +their own authors judged correct, and appear here only so you do not have to +find them by reading the whole file: + +- **`@cipherstash/stack` — `clientKey` is hex-only.** A decoder fallback that + also accepted standard padded base64 is gone, and such a key is now rejected + at client construction with `invalid clientKey: expected a hex-encoded key`. + Hex is what `stash env` emits and what the docs have always specified, so most + callers are unaffected; a key pasted out of `~/.cipherstash/secretkey.json` + (which stores base64) is not. See "Adopt protect-ffi 0.31.0" under Patch + Changes. That entry also narrows which `error.code` values DynamoDB + operations report. +- **`stash` — `stash eql validate` lost `--exclude-operator-family`,** and two + checks that used to exit 1 no longer do. A script passing that flag, or a CI + gate relying on those exit codes, needs updating. See the `eql validate` entry + under Minor Changes. -**If you do not use `@cipherstash/stack-prisma`, this release is additive.** -Read your package's own Minor and Patch entries below for what actually changed -in it. +If you use neither `@cipherstash/stack-prisma` nor either of those, upgrading +1.x → 2.0.0 needs no code changes. diff --git a/packages/protect-ffi/CHANGELOG.md b/packages/protect-ffi/CHANGELOG.md index 9956ed1ba..ebfe25a1a 100644 --- a/packages/protect-ffi/CHANGELOG.md +++ b/packages/protect-ffi/CHANGELOG.md @@ -1,8 +1,8 @@ # Changelog -## About the entries below 0.31.0 +## About 0.31.0 and earlier -Everything from `[0.31.0]` down was written by hand, under an `[Unreleased]` +Every entry from `[0.31.0]` down was written by hand, under an `[Unreleased]` heading that an npm `version` lifecycle hook promoted on release. Those entries follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), with a `Breaking` heading added for the pre-1.0 convention of shipping breaking changes @@ -13,16 +13,19 @@ monorepo, Changesets generates every entry above this heading from the changesets in a release, in its own format. ## [0.31.0] - 2026-07-27 diff --git a/packages/protect-ffi/package.json b/packages/protect-ffi/package.json index e24b2ced8..6b97a427c 100644 --- a/packages/protect-ffi/package.json +++ b/packages/protect-ffi/package.json @@ -73,7 +73,8 @@ "dist/wasm/protect_ffi_bg.wasm.d.ts", "dist/wasm/protect_ffi_inline.js", "dist/wasm/errors.js", - "dist/wasm/errors.d.ts" + "dist/wasm/errors.d.ts", + "CHANGELOG.md" ], "neon": { "type": "library", diff --git a/packages/protect-ffi/platforms/darwin-arm64/package.json b/packages/protect-ffi/platforms/darwin-arm64/package.json index 2dfa7aff0..d911e246d 100644 --- a/packages/protect-ffi/platforms/darwin-arm64/package.json +++ b/packages/protect-ffi/platforms/darwin-arm64/package.json @@ -15,7 +15,8 @@ ], "main": "index.node", "files": [ - "index.node" + "index.node", + "CHANGELOG.md" ], "neon": { "type": "binary", diff --git a/packages/protect-ffi/platforms/darwin-x64/package.json b/packages/protect-ffi/platforms/darwin-x64/package.json index 9f288cdcd..29be22966 100644 --- a/packages/protect-ffi/platforms/darwin-x64/package.json +++ b/packages/protect-ffi/platforms/darwin-x64/package.json @@ -15,7 +15,8 @@ ], "main": "index.node", "files": [ - "index.node" + "index.node", + "CHANGELOG.md" ], "neon": { "type": "binary", diff --git a/packages/protect-ffi/platforms/linux-arm64-gnu/package.json b/packages/protect-ffi/platforms/linux-arm64-gnu/package.json index 3b4933598..c5f7771f5 100644 --- a/packages/protect-ffi/platforms/linux-arm64-gnu/package.json +++ b/packages/protect-ffi/platforms/linux-arm64-gnu/package.json @@ -15,7 +15,8 @@ ], "main": "index.node", "files": [ - "index.node" + "index.node", + "CHANGELOG.md" ], "neon": { "type": "binary", diff --git a/packages/protect-ffi/platforms/linux-x64-gnu/package.json b/packages/protect-ffi/platforms/linux-x64-gnu/package.json index 44c695c09..e6635b39c 100644 --- a/packages/protect-ffi/platforms/linux-x64-gnu/package.json +++ b/packages/protect-ffi/platforms/linux-x64-gnu/package.json @@ -15,7 +15,8 @@ ], "main": "index.node", "files": [ - "index.node" + "index.node", + "CHANGELOG.md" ], "neon": { "type": "binary", diff --git a/packages/protect-ffi/platforms/linux-x64-musl/package.json b/packages/protect-ffi/platforms/linux-x64-musl/package.json index 0c427e61d..833f0374e 100644 --- a/packages/protect-ffi/platforms/linux-x64-musl/package.json +++ b/packages/protect-ffi/platforms/linux-x64-musl/package.json @@ -15,7 +15,8 @@ ], "main": "index.node", "files": [ - "index.node" + "index.node", + "CHANGELOG.md" ], "neon": { "type": "binary", diff --git a/packages/protect-ffi/platforms/win32-x64-msvc/package.json b/packages/protect-ffi/platforms/win32-x64-msvc/package.json index 37116ed34..3a80a838d 100644 --- a/packages/protect-ffi/platforms/win32-x64-msvc/package.json +++ b/packages/protect-ffi/platforms/win32-x64-msvc/package.json @@ -15,7 +15,8 @@ ], "main": "index.node", "files": [ - "index.node" + "index.node", + "CHANGELOG.md" ], "neon": { "type": "binary", diff --git a/packages/stack-drizzle/package.json b/packages/stack-drizzle/package.json index b67ee7bf7..ec60d110a 100644 --- a/packages/stack-drizzle/package.json +++ b/packages/stack-drizzle/package.json @@ -30,7 +30,8 @@ "sideEffects": false, "files": [ "dist", - "README.md" + "README.md", + "CHANGELOG.md" ], "exports": { ".": { diff --git a/packages/stack-prisma/package.json b/packages/stack-prisma/package.json index f7114280f..18f59369c 100644 --- a/packages/stack-prisma/package.json +++ b/packages/stack-prisma/package.json @@ -62,7 +62,8 @@ "files": [ "dist", "src", - "README.md" + "README.md", + "CHANGELOG.md" ], "scripts": { "build": "tsup", diff --git a/packages/stack-supabase/package.json b/packages/stack-supabase/package.json index 5520ba9d7..3b5092cf6 100644 --- a/packages/stack-supabase/package.json +++ b/packages/stack-supabase/package.json @@ -29,7 +29,8 @@ "sideEffects": false, "files": [ "dist", - "README.md" + "README.md", + "CHANGELOG.md" ], "exports": { ".": { From d200ae6a855857895474ba59720c70198836e670 Mon Sep 17 00:00:00 2001 From: Toby Hede Date: Wed, 19 Aug 2026 12:42:03 +1000 Subject: [PATCH 3/3] fix(release): resolve the cross-package changelog references, and correct two stale changelog identities MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit **The references dangled in three of the five packages they render into.** The alignment note pointed readers at "Adopt protect-ffi 0.31.0 under Patch Changes" and "the `eql validate` entry under Minor Changes". Those sections exist in `@cipherstash/stack`'s and `stash`'s changelogs — not in `stack-drizzle`'s, `stack-supabase`'s or `wizard`'s, where the same entry is also rendered, and where `wizard@2.0.0` has no other sections at all. Each reference now names the package whose changelog holds it, so it resolves from wherever it is read. **`packages/stack-prisma/CHANGELOG.md` still identified itself as `@cipherstash/prisma-next`**, stale since the rename in #844. Harmless while the file stayed out of the tarball; adding it to `files` in the previous commit made it customer-visible, so the heading is corrected in the same release that starts shipping it. **`packages/cli/CHANGELOG.md` had the same defect and was already shipping it.** Its heading read `@cipherstash/cli`, a name that does not exist on npm — the package is `stash`, and this file has been in its `files` list all along. Not caused by this PR, but it is one line and the same class of error. All six published Stack packages now have a changelog heading matching their package name. Verified by running `changeset version` and rolling it back: no "under Patch Changes" / "under Minor Changes" reference survives anywhere, and `wizard@2.0.0` — which has no entries of its own — renders both references naming `@cipherstash/stack` and `stash`. Versions unchanged. `test:scripts` 416 passing. --- .changeset/stack-2-0-0-version-alignment.md | 18 +++++++++--------- packages/cli/CHANGELOG.md | 2 +- packages/stack-prisma/CHANGELOG.md | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/.changeset/stack-2-0-0-version-alignment.md b/.changeset/stack-2-0-0-version-alignment.md index 373f6108a..2c7064bfc 100644 --- a/.changeset/stack-2-0-0-version-alignment.md +++ b/.changeset/stack-2-0-0-version-alignment.md @@ -25,23 +25,23 @@ shipping alone would leave the CLI recommending versions that no longer match what is published, and warning about a skew it had itself created. **This does not mean every package in the release is drop-in.** The version -number is shared; the changes are not. Two entries below need action from some -users, and neither is filed under Major Changes — they are recorded at the level -their own authors judged correct, and appear here only so you do not have to -find them by reading the whole file: +number is shared; the changes are not. Two changes elsewhere in this release +need action from some users, and neither is filed under Major Changes — each is +recorded at the level its own author judged correct. They are named here so you +do not have to read six changelogs to find them: - **`@cipherstash/stack` — `clientKey` is hex-only.** A decoder fallback that also accepted standard padded base64 is gone, and such a key is now rejected at client construction with `invalid clientKey: expected a hex-encoded key`. Hex is what `stash env` emits and what the docs have always specified, so most callers are unaffected; a key pasted out of `~/.cipherstash/secretkey.json` - (which stores base64) is not. See "Adopt protect-ffi 0.31.0" under Patch - Changes. That entry also narrows which `error.code` values DynamoDB - operations report. + (which stores base64) is not. The full entry is "Adopt protect-ffi 0.31.0" in + the **`@cipherstash/stack`** changelog; it also narrows which `error.code` + values DynamoDB operations report. - **`stash` — `stash eql validate` lost `--exclude-operator-family`,** and two checks that used to exit 1 no longer do. A script passing that flag, or a CI - gate relying on those exit codes, needs updating. See the `eql validate` entry - under Minor Changes. + gate relying on those exit codes, needs updating. The full entry is under + `eql validate` in the **`stash`** changelog. If you use neither `@cipherstash/stack-prisma` nor either of those, upgrading 1.x → 2.0.0 needs no code changes. diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index 488315751..0bd312d24 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,4 +1,4 @@ -# @cipherstash/cli +# stash ## 1.0.0 diff --git a/packages/stack-prisma/CHANGELOG.md b/packages/stack-prisma/CHANGELOG.md index 6a06cbe06..bae13f9f5 100644 --- a/packages/stack-prisma/CHANGELOG.md +++ b/packages/stack-prisma/CHANGELOG.md @@ -1,4 +1,4 @@ -# @cipherstash/prisma-next +# @cipherstash/stack-prisma ## 1.0.0