build(deps-dev): bump vitest and @vitest/coverage-v8 #136
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [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). These dependencies needed to be updated together. Updates `vitest` from 0.34.6 to 1.0.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.0.1/packages/vitest) Updates `@vitest/coverage-v8` from 0.34.6 to 1.0.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.0.1/packages/coverage-v8) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-major - dependency-name: "@vitest/coverage-v8" dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
|
Kudos, SonarCloud Quality Gate passed!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #136 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 650 650
Branches 46 46
=========================================
Hits 650 650
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again. Next stepsWhat is a chronological version anomaly?Semantic versions published out of chronological order. This could either indicate dependency confusion or a patched vulnerability. What is dynamic require?Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution. Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code. What is environment variable access?Package accesses environment variables, which may be a sign of credential stuffing or data theft. Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. What is filesystem access?Accesses the file system, and could potentially read sensitive data. If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. What is a mixed license?(Experimental) Package contains multiple licenses. A new version of the package should be published that includes a single license. Consumers may seek clarification from the package author. Ensure that the license details are consistent across the LICENSE file, package.json license field and license details mentioned in the README. What is eval?Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior. Avoid packages that use eval, since this could potentially execute any code. What is an empty package?Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish. Remove dependencies that do not export any code or functionality and ensure the package version includes all of the files it is supposed to. What is a major refactor?Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes. Consider waiting before upgrading to see if any issues are discovered, or be prepared to scrutinize any bugs or subtle changes the major refactor may bring. Publishers my consider publishing beta versions of major refactors to limit disruption to parties interested in the new changes. What is wrong with semver < v1?Package is not semver >=1. This means it is not stable and does not support ^ ranges. If the package sees any general use, it should begin releasing at version 1.0.0 or later to benefit from semver. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Bumps vitest and @vitest/coverage-v8. These dependencies needed to be updated together.
Updates
vitestfrom 0.34.6 to 1.0.1Release notes
Sourced from vitest's releases.
... (truncated)
Commits
0802167chore: release v1.0.1420707ffix: bump vitest packagespeerDependenciesversions (#4654)34517cechore: release v1.0.0f35e2c7refactor: replaceos.cpuswithos.availableParallelism(#4639)da7949dfix(jsdom): don't go into an infinite recusion when calling atob39c952achore(deps): update dependency@types/micromatchto ^4.0.6 (#4647)05b0521fix(vitest): independently mock each instance's methods for mocked class (#4564)eca25dcfix: set process name for idle workers (#4641)54d52d4fix(vm): remove sequencer usage from createVmThreadsPool function (#4638)ceca93ddocs:os.cpu()should beos.cpus()(#4634)Updates
@vitest/coverage-v8from 0.34.6 to 1.0.1Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
0802167chore: release v1.0.1420707ffix: bump vitest packagespeerDependenciesversions (#4654)34517cechore: release v1.0.04166c41fix(coverage): improve memory usage by writing temporary files on file system...b766d34chore: release v1.0.0-beta.61fdd6fefix(deps): update dependency std-env to ^3.5.0 (#4582)a70f216fix(deps): update dependency v8-to-istanbul to ^9.2.0 (#4583)abe6c72chore: release v1.0.0-beta.54953410feat!(coverage): glob based coverage thresholds (#4442)fb84885chore: add defaults to exports (#4462)You can trigger a rebase of this PR 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)