chore(release): v0.26.0 - #335
wmadden-electric wants to merge 1 commit into
Conversation
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>
|
✅ Gizmo reviewed de5f568 — posted 0 inline comment(s) this pass. Open findings: none Change walkthroughThis PR is the release bump for v0.26.0: 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 Version consistency. The bump is complete and internally consistent: all 41 workspace packages report Surfaces that follow the release. skills/prisma-composer-core-concepts/SKILL.md:5 tracks the new 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. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Comment |
commit: |
Release v0.26.0. Merging this PR runs the
Publish to npmworkflow. It publishes@prisma/composer,@prisma/composer-prisma-cloudand@prisma/composer-cliat0.26.0under thelatesttag, and creates a GitHub Release with generated notes.What ships
Changes merged since v0.25.0:
composersection ofprisma.config.ts.DEPLOY.ENGINE_FAILED.composer-clibuilds against@prisma/cli-engine0.6.2, the engine the nextprismaCLI ships.What changed in this PR
pnpm bump-minorset every workspacepackage.jsonto0.26.0and rewrote internalworkspace:dependencies to match. The lockfile and thelibrary_versionin the core-concepts skill follow.pnpm check:publish-depspasses.Agent: narcissus-93
🤖 Generated with Claude Code