Keep the next tag resolving instead of removing it - #231
Merged
Conversation
…ing it Operator ruling 2026-08-25: removing the tag breaks every prisma@next instruction immediately, while a manually re-pointed tag that lags between moves still resolves a complete, working release. The tag is retired with an announcement once 8.0.0 stable ships. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Warning Review limit reachedNext included review available in 15 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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 |
commit: |
The stale product dev tag that blocked the rc.10 release run, and the open @prisma/cli deprecation decision. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
The registry maintenance is four npm dist-tag commands the operator runs once; a committed script outlives its single use. The versioning doc names the command shape instead. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
wmadden-electric
force-pushed
the
claude/next-tag-keeps-resolving
branch
from
August 25, 2026 11:05
efcdf17 to
1603ed9
Compare
wmadden
approved these changes
Aug 25, 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.
Follow-up to #230, applying the operator ruling of 2026-08-25: removing
nextwould break everyprisma@nextinstruction immediately (npm install prisma@nextfails with no matching version), while a manually re-pointed tag that lags between moves still resolves a complete, working release — exact pins make every published version internally coherent.scripts/cutover-dist-tags.shnow pointsnextat the current release (8.0.0-rc.10) onprismaand@prisma/cli, and at 0.2.3 on the engine, instead of removing the tag.docs/oss/versioning.mdrecords the policy:nextis kept alive, moved by hand, allowed to lag, and retired with an announcement once8.0.0stable ships. New text should say plainprisma.Docs and a maintenance script only — no published behavior changes until the operator runs the script.
🤖 Generated with Claude Code