chore: update dependencies to latest compatible versions - #17
Merged
Conversation
typescript stays on 6.x: 7.0 still breaks eslint and the unbuild dts step. c12 stays on 3.x because its latest tag is a 4.0 beta.
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.
What
Moves every dependency to the newest version that still works, plus a lockfile refresh of transitives.
Three things were deliberately left behind:
tsc --noEmitpasses, buteslintcrashes andunbuildfails insiderollup-plugin-dts, both because 7.0 shipped without the JS compiler API. This is the case the ignore rule independabot.ymlalready describes.latesttag points today, but it is a prerelease.minimum-release-agein.npmrcskipped it. It will land on its own.Why
Nothing had been updated in a while. Doing it in one pass now means the weekly dependabot PR stays small.
Typecheck, lint, the 720 tests, and the build all pass on these versions.
One known audit finding
pnpm auditreports one high: nanoid <3.3.18 (GHSA-2v37-7h3g-55p8), reached through@antfu/eslint-config > eslint-processor-vue-blocks > @vue/compiler-sfc > postcss > nanoid.Left as is on purpose. It is devDependencies only (
pnpm why nanoid --prodis empty, and nanoid does not appear indist/), so nothing reaches users. The patched 3.3.18 was published a couple of hours ago and postcss already allows it, so the only thing holding it back is our own 7 day cooldown. It will come in next week.