Hotfix: pin TipTap suite to 3.27.0 for deploy release-age policy (v0.3.27)#30
Merged
Conversation
The deploy environment enforces a minimum-release-age policy and rejected the lockfile: @tiptap/*@3.28.0 was published ~5 hours before we installed it. Pin the whole suite to 3.27.0 (published 2026-06-17, ~4 weeks old) via exact deps + pnpm overrides, since the extension packages' internal ^3.27 ranges and peer resolution otherwise float transitive @tiptap/* back to the newest release. @tiptap/core added as a direct pinned dep so peer resolution uses the root instance. No API changes for our usage — TableKit, TaskList/TaskItem, Markdown (contentType/getMarkdown) all present at 3.27.0. Bump to a newer patch once it ages past the policy window. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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
The deploy environment's minimum-release-age (supply-chain freshness) policy rejected the lockfile from #29: the entire
@tiptap/*@3.28.0suite was published ~5 hours beforepnpm addresolved it.pnpm.overridesfor all 27@tiptap/*packages, because the extensions' internal^3.27ranges and peer resolution otherwise float transitives back to newest;@tiptap/coreadded as a direct pinned dep so peer resolution uses the root instance.TableKit,TaskList/TaskItem,Markdown(contentType: 'markdown'/getMarkdown()) all verified present at 3.27.0.Lockfile contains zero
3.28.0references. 167/167 tests, tsc clean, editor pages render.Once 3.28.x ages past the policy window, a routine
pnpm updateof the pins can pick it up.🤖 Generated with Claude Code