The Version Packages PR would publish the Prisma 8 rebuild as 0.44.0, not the major its changesets describe #1650

Found in pre-release QA of main at 7ffacbf (the unreleased Prisma 8 rebuild).

Severity: medium
Triage: needs-triage. Choosing the release version is a maintainer decision.

pnpm changeset status --verbose shows every @opensaas/stack-* package going to 0.44.0 and create-opensaas-app to 0.4.0, and the open Version Packages PR #1448 proposes exactly that. .changeset/quiet-otters-project.md documents real breaking changes and says they ship on minor "because the whole Prisma 8 line is released as one major at the end of it". No changeset declares major, and nothing in the repo stages or enforces that final bump. The release workflow publishes whatever the merged Version Packages PR says.

Under 0.x versioning a caret range such as ^0.43.0 does not resolve to 0.44.0, so existing installs will not upgrade silently either way. The open question is whether this release should be 1.0.0, as the changesets describe, or 0.44.0.

Options:

• Add a major changeset for the fixed @opensaas/stack-* group before merging Version Packages #1448, if the intent is 1.0.0.
• Or update the changeset text so it stops promising a major release.

Generated by Claude Code