-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): bump dprint from 0.35.1 to 0.41.0 #47
base: master
Are you sure you want to change the base?
Conversation
Bumps [dprint](https://github.com/dprint/dprint) from 0.35.1 to 0.41.0. - [Release notes](https://github.com/dprint/dprint/releases) - [Commits](dprint/dprint@0.35.1...0.41.0) --- updated-dependencies: - dependency-name: dprint dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Dependabot tried to add
|
The following labels could not be found: |
|
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 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 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 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. 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 dprint from 0.35.1 to 0.41.0.
Release notes
Sourced from dprint's releases.
... (truncated)
Commits
66db547
0.41.04e0da2d
fix: log and ignore PermissionDenied errors when globbing (#748)6dbaea4
docs: fix plugin_info.rs comment (#746)c095c82
fix: show anchor name in trace output (#747)6549a48
feat: monitor and throttle CPU if necessary (#744)abf03b8
fix: key Wasm cache on CPU features (#739)b56659b
chore: re-enable integration test (#733)bdb4e2a
chore: fix upgrade message and bump dprint-core version6d10b5e
0.40.2b7289ee
fix: improve error message when process plugin is too old (#732)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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)