build(deps-dev): bump semantic-release from 21.0.2 to 21.0.7 #40
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [semantic-release](https://github.com/semantic-release/semantic-release) from 21.0.2 to 21.0.7. - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v21.0.2...v21.0.7) --- updated-dependencies: - dependency-name: semantic-release dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
|
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 does no tests mean?Package does not have any tests. This is a strong signal of a poorly maintained or low quality package. Add tests and publish a new version of the package. Consumers may look for an alternative package with better testing. Why is contributor and author data important?Package does not specify a list of contributors or an author in package.json. Add a author field or contributors array to package.json. What is network access?This module accesses the network. Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. What are URL strings?Package contains fragments of external URLs or IP addresses, which may indicate that it covertly exfiltrates data. Avoid using packages that make connections to the network, since this helps to leak data. What is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What are unmaintained packages?Package has not been updated in more than a year and may be unmaintained. Problems with the package may go unaddressed. Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance. Why are READMEs important?Package does not have a README. This may indicate a failed publish or a low quality package. Add a README to to the package and publish a new version. 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 are trivial packages?Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency. Removing this package as a dependency and implementing its logic will reduce supply chain risk. 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
|
|
Looks like semantic-release is no longer a dependency, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/semantic-release-21.0.7
branch
Bumps semantic-release from 21.0.2 to 21.0.7.
Release notes
Sourced from semantic-release's releases.
... (truncated)
Commits
70996e0fix(deps): update dependency read-pkg-up to v10 (#2862)40dbf56ci(action): update actions/checkout action to v3.5.3 (#2852)3159c97chore(deps): lock file maintenance (#2849)41e7027ci(action): update actions/upload-artifact action to v3.1.2 (#2851)e4229f9fix: get correct version if prerelease branch shares version with ... (#2416)9514e20ci(action): update ossf/scorecard-action action to v2.2.0 (#2854)5fcdc27ci(action): update github/codeql-action action to v2.20.1 (#2853)1260d3aci(action): pin dependencies (#2850)9ebabe1ci(ossf-scorecard): added workflow calculating scorecard metrics (#2848)e39ae90test(integration): properly waited for the image pulls to complete (#2842)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 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)