feat: rename @cipherstash/prisma-next to @cipherstash/stack-prisma for 1.0 - #844
Merged
Conversation
🦋 Changeset detectedLatest commit: 9effcf1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedToo many files! This PR contains 190 files, which is 90 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (190)
You can disable this status message by setting the 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. Comment |
tobyhede
approved these changes
Jul 30, 2026
… to @cipherstash/stack-prisma Closes #842 (revised plan: all adapters use the stack- prefix). - @cipherstash/prisma-next -> @cipherstash/stack-prisma (dir packages/stack-prisma), matching @cipherstash/stack-drizzle and @cipherstash/stack-supabase, which keep their names. - skills/stash-prisma-next -> skills/stash-prisma; CLI/wizard skill maps, install-deps, release-train manifests, workflows, docs, and SECURITY.md updated to match. - examples/prisma package renamed @cipherstash/prisma-next-example -> @cipherstash/prisma-example. The prisma-next provider id, --prisma-next init flag, and prisma-next.config.ts detection are unchanged - they name the external Prisma Next framework (@prisma-next/*), not our package. Retained changesets and .changeset/{config,pre}.json are rewritten to the new name so the pre-mode exit in #843 versions and publishes @cipherstash/stack-prisma as 1.0.0 (the name is unclaimed on npm).
coderdan
force-pushed
the
feat/842-rename-packages-1-0
branch
from
July 30, 2026 03:40
755acc4 to
9effcf1
Compare
coderdan
changed the title
This was referenced Jul 30, 2026
This was referenced Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Closes #842 (revised plan — all adapters share the
stack-prefix so names and versions stay consistent):@cipherstash/prisma-next@cipherstash/stack-prisma(dirpackages/stack-prisma)@cipherstash/stack-drizzle@cipherstash/stack-supabase@cipherstash/stack-prismais unclaimed on npm, so it publishes cleanly as1.0.0. (The originally-discussed bare names were dropped: legacy pre-Stack@cipherstash/drizzleoccupies its bare name up to3.0.3, which would have blocked a1.0.0publish and split the fixed release train.)What deliberately did NOT rename
prisma-nextas a term survives where it names the external Prisma Next framework (@prisma-next/*), not our package: thestash init --prisma-nextflag and provider id,prisma-next.config.tsdetection instash eql install, and every mention of theprisma-nextCLI. Only our extension package is renamed.Scope
package.jsonname +repository.directory, dirgit mved, workspace deps, lockfile regeneratedpackages/cli:release-train.tsmanifest map,install-deps.tspackage map,install-skills.tsskill sets, messages, provider next-stepsskills/stash-prisma-next→skills/stash-prisma; content ofstash-prisma,stash-encryption,stash-deployment,stash-cliupdated to the new name.changeset/config.jsonfixed group and.changeset/pre.jsoninitialVersionskeys — so the pre-mode exit in chore(release): exit changesets pre mode — next release is 1.0.0 #843 versions and publishes@cipherstash/stack-prisma@1.0.0. New changesetrename-packages-1-0.mdrecords the rename in the 1.0.0 changelog.integration-prisma-next.yml,tests.yml,prisma-*-e2e.yml), dependabot, path lints,scripts/__tests__AGENTS.mdrepository layout + skill map,SECURITY.mdpackage tableexamples/prismadep renamed; example package name@cipherstash/prisma-next-example→@cipherstash/prisma-exampleFollow-ups
npm deprecate @cipherstash/prisma-nextpointing at@cipherstash/stack-prisma; publish the prepared@cipherstash/drizzle@3.0.4README republish pointing the legacy package at@cipherstash/stack-drizzle.Verification
pnpm --filter stash test— 895 passed;pnpm --filter stash test:e2e— pty suite passedpnpm --filter @cipherstash/stack-prisma test— 344 passedpnpm --filter @cipherstash/wizard test— 342 passedpnpm run test:scripts— 178 passed;lint:package-pathsclean;code:fixerror-freechangeset versionsimulation (on chore(release): exit changesets pre mode — next release is 1.0.0 #843's merged branch): whole train graduates to 1.0.0,pre.jsonconsumed@cipherstash/prisma-nextreferences remain outside CHANGELOGs and dated design docs