chore(deps): bump the dependencies group with 2 updates #157
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 dependencies group with 2 updates: @nodesecure/rc and @nodesecure/vulnera.
Updates
@nodesecure/rc
from 3.0.0 to 4.0.0Release notes
Sourced from
@nodesecure/rc
's releases.Commits
624052d
4.0.041a3c85
chore!: update to@nodesecure/vulnera
2.0.0 (#250)860b315
chore(deps): bump the github-actions group with 5 updates (#249)Updates
@nodesecure/vulnera
from 1.8.0 to 2.0.1Release notes
Sourced from
@nodesecure/vulnera
's releases.... (truncated)
Commits
80fe49e
2.0.1b5ae3e0
fix(package.json): only includes ./dist in tarball whitelist (#261)5f03de8
2.0.06fd487e
fix(pnpm): add missing virtualStoreDirMaxLength (#260)224ec62
chore(deps-dev): bump the development-dependencies group across 1 directory w...0b6e61c
chore(deps): bump@nodesecure/npm-registry-sdk
in the dependencies group (#255)8157656
chore(deps): bump the github-actions group with 6 updates (#258)9e94e3e
chore(deps-dev): bump c8 in the development-dependencies group (#252)cc29074
chore(deps): bump the dependencies group across 1 directory with 3 updates (#...57d1942
chore(deps): bump the github-actions group across 1 directory with 5 updates ...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 <dependency name> major version
will 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 version
will 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