Repository navigation
chore(deps): upgrade vitest and @vitest/coverage-v8 to 5.0.5 - #296
Merged
Merged
Conversation
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.
Summary
Upgrades
vitestand@vitest/coverage-v8together to 5.0.5 (exact pins).@vitest/coverage-v8peers on an exactvitestversion, so the two have to move in lockstep.vitestays at 8.3.4: vitest 5's peer range is^6.4 || ^7 || ^8.Dependabot now groups the pair, so future updates arrive as one PR that installs cleanly.
Changes
TaskFlow.Web/package.json:vitestand@vitest/coverage-v8pinned to5.0.5, with no caret because the peer is exact.TaskFlow.Web/package-lock.json: regenerated. Churn is limited to vitest,@vitest/*and their transitive packages. vite, plugin-react, jsdom, testing-library, typescript and@types/nodeare unchanged..github/dependabot.yml(npm block):vitestand@vitest/coverage-v8ignores.@hey-api/*major ignores.vitestgroup (vitest,@vitest/*) with noupdate-types, so it covers major, minor and patch.exclude-patternsfor the same two tonpm-minor-patch, so each package is in exactly one group.TaskFlow.Web/src/test/jest-dom.d.ts(new, types only): vitest 5 changedAssertion<T>toAssertion<R, T>and exposesMatchers<R, T>for custom matchers.@testing-library/jest-dom7.0.1 still targets the old shape, and without this shimnpm run type-checkfails with about 450TS2339errors such asProperty 'toBeInTheDocument' does not exist. The file augments vitest'sMatchers<R, T>with jest-dom'sTestingLibraryMatchers. It can be removed once jest-dom ships vitest 5 typings.No test file,
vite.config.ts, doc, workflow, Dockerfile or backend change. The 80% coverage threshold is unchanged.Verification (local)
npm cinpm run lintTasksPage.tsx:287)npm run type-checknpm run test -- --run --coveragenpm run buildnpm audit --omit=devSkip/todo count is unchanged, and no test was edited.
Not verified locally
UNABLE_TO_GET_ISSUER_CERT_LOCALLYinnpm ci, andserver certificate not trustedinapk upgrade), which look like a corporate proxy. Neither failure involves this diff. Trivy is not installed locally.security-scan.ymlin CI is the gate. The runtime image copies all ofnode_modules, including dev dependencies, so new transitive packages are scanned.^22.12 || ^24 || >=26). CI and Docker use Node 26.Notes
vite.config.tsuses__dirname, whichconfigLoader: 'native'does not support. It is not an error, andvite.config.tsis out of scope here.Closes #285