Repository navigation
chore(docs): pin npm dependencies to exact versions (SITE14) - #984
Merged
Merged
Conversation
… (SITE14) Co-Authored-By: Claude Sonnet 5.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
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.
Applies ct-conventions rule
SITE14(control-toolbox/ct-conventions#30): every dependency indocs/package.jsonis pinned to an exact version, no^.There is no lockfile and DocumenterVitepress runs a plain
npm install, so ranges pick up the latest release at each build (this broke the docs build with@nolebase/vitepress-plugin-enhanced-readabilities@2.21.x).Versions are the ones
npm installcurrently resolves; no version change in practice except patch/minor bumps already in range.npm installverified in a clean directory.🤖 Generated with Claude Code