Skip to content

chore(release): v0.26.0 - #335

Closed
wmadden-electric wants to merge 1 commit into
mainfrom
chore/release-v0.26.0
Closed

wmadden-electric wants to merge 1 commit into
mainfrom
chore/release-v0.26.0

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

Release v0.26.0. Merging this PR runs the Publish to npm workflow. It publishes @prisma/composer, @prisma/composer-prisma-cloud and @prisma/composer-cli at 0.26.0 under the latest tag, and creates a GitHub Release with generated notes.

npm install @prisma/composer@0.26.0

What ships

Changes merged since v0.25.0:

What changed in this PR

pnpm bump-minor set every workspace package.json to 0.26.0 and rewrote internal workspace: dependencies to match. The lockfile and the library_version in the core-concepts skill follow. pnpm check:publish-deps passes.

Agent: narcissus-93

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@prisma-gizmo

prisma-gizmo Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

✅ Gizmo reviewed de5f568 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR is the release bump for v0.26.0: pnpm bump-minor read the root package.json version at HEAD (0.25.0), computed the next minor, and rewrote every workspace manifest and the lockfile to 0.26.0 so the merge can publish @prisma/composer, @prisma/composer-prisma-cloud, and @prisma/composer-cli under the latest tag.

Mechanics. The change follows the repo's scripted release path exactly: scripts/bump-minor.ts delegates to scripts/set-version.ts and regenerates pnpm-lock.yaml, so CI's --frozen-lockfile install and the check:publish-deps tarball gate stay satisfied. Every manifest is pinned to the literal workspace:0.26.0 form the publish-time exact-pin check expects for shipped dependencies.

Version consistency. The bump is complete and internally consistent: all 41 workspace packages report 0.26.0, every internal workspace: specifier matches its target package's actual version (including cross-references like @prisma/example-store consumed by the integration tests), all 160 lockfile specifiers read workspace:0.26.0, and no 0.25.0 reference survives anywhere outside node_modules. The only manifest left at a non-0.26.0 version is a vendored Convex inspiration example under docs/design/, which is not a workspace package. No other package.json field was touched — external pins (@prisma/cli-engine 0.6.2, alchemy, Effect/ORM pre-releases) are unchanged.

Surfaces that follow the release. skills/prisma-composer-core-concepts/SKILL.md:5 tracks the new library_version, keeping the skill's declared library version in lockstep with the published @prisma/composer. The root package.json holds the canonical 0.26.0 that bump-minor will read as the base for the next cycle.

Scope. The diff contains no code, workflow, or documentation changes beyond the version fields and the skill frontmatter — it ships the behavior already merged since v0.25.0 (#328, #334, #326, #325) under the new version numbers.

@coderabbitai

coderabbitai Bot commented Oct 5, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 47a7b9e9-d38f-4bd1-a16b-dd6de3e914c5
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@pkg-pr-new

pkg-pr-new Bot commented Oct 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@335
npm i https://pkg.pr.new/@prisma/composer-cli@335
npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@335

commit: de5f568

@prisma-gizmo prisma-gizmo Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New findings: none · trace

@prisma-gizmo prisma-gizmo Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All Gizmo review threads are resolved and the head commit has been reviewed. Approving.

@wmadden-electric

Copy link
Copy Markdown
Contributor Author

Closing: this PR is no longer needed. #331 also set the version to 0.26.0. When it merged (a91a6dc), the Publish to npm workflow published v0.26.0 to npm under latest and created the GitHub Release. That release includes every change listed here, plus #331.

@wmadden-electric
wmadden-electric deleted the chore/release-v0.26.0 branch October 5, 2026 14:43
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