chore(deps-dev): bump the development-dependencies group in /demo-app with 3 updates#53
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
bot
added
the
dependencies
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/demo-app/development-dependencies-3c36b61e2a
branch
from
f18d5da to
0908500
Compare
Bumps the development-dependencies group in /demo-app with 3 updates: [eslint](https://github.com/eslint/eslint), [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8). Updates `eslint` from 8.57.1 to 9.39.1 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v8.57.1...v9.39.1) Updates `vitest` from 2.1.9 to 4.0.13 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.13/packages/vitest) Updates `@vitest/coverage-v8` from 2.1.9 to 4.0.13 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.13/packages/coverage-v8) --- updated-dependencies: - dependency-name: eslint dependency-version: 9.39.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: development-dependencies - dependency-name: vitest dependency-version: 4.0.13 dependency-type: direct:development update-type: version-update:semver-major dependency-group: development-dependencies - dependency-name: "@vitest/coverage-v8" dependency-version: 4.0.13 dependency-type: direct:development update-type: version-update:semver-major dependency-group: development-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/demo-app/development-dependencies-3c36b61e2a
branch
from
0908500 to
dc61367
Compare
Author
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
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.
Bumps the development-dependencies group in /demo-app with 3 updates: eslint, vitest and @vitest/coverage-v8.
Updates
eslintfrom 8.57.1 to 9.39.1Release notes
Sourced from eslint's releases.
... (truncated)
Commits
e2772819.39.14cdf397Build: changelog update for 9.39.192db329chore: update@eslint/jsversion to 9.39.1 (#20284)c7ebefcchore: package.json update for@eslint/jsrelease650753efix: Only pass node to JS lang visitor methods (#20283)51b51f4docs: add a section on when to use extends vs cascading (#20268)61778f6chore: update eslint-config-eslint dependency@eslint/jsto ^9.39.0 (#20275)d9ca2fcci: Add rangeStrategy to eslint group in renovate config (#20266)009e507test: fix version tests for ESLint v10 (#20274)b44d426docs: Update READMEUpdates
vitestfrom 2.1.9 to 4.0.13Release notes
Sourced from vitest's releases.
... (truncated)
Commits
73b54cechore: release v4.0.13b27e002perf: avoid fetchModule roundtrip if the module is cached (#9075)6b9a1b5perf(experimental): iffsCacheModuleis enabled, read from the memory when ...332afa0fix(types): don't import node.js dependent types in vitest/browser (#9068)6356b1dfix(types): don't use type from Vite 7.1 (#9071)5aa84d5chore: release v4.0.12e944a37fix: don't import from@opentelemetry/apiin public types (#9066)9a8bc78fix: inheritfsModuleCachePathby default (#9063)c3befb0chore: release v4.0.111b14737perf(experimental): add file system cache (#9026)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.
Updates
@vitest/coverage-v8from 2.1.9 to 4.0.13Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
73b54cechore: release v4.0.135aa84d5chore: release v4.0.12c3befb0chore: release v4.0.11259a3d1chore: release v4.0.1062fab24chore: release v4.0.946bfd09chore: release v4.0.8da8b93afix(deps): update all non-major dependencies (#8636)1f5d9d2chore: release v4.0.72e7b2b8chore: release v4.0.6e3b7775fix(coverage): prevent filtering out virtual files before remapping to source...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@vitest/coverage-v8since your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions