-
Notifications
You must be signed in to change notification settings - Fork 1
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
build(deps): bump @nuxt/content from 2.12.0 to 2.12.1 in /docs #196
build(deps): bump @nuxt/content from 2.12.0 to 2.12.1 in /docs #196
Conversation
@dependabot squash and merge |
One of your CI runs failed on this pull request, so Dependabot won't merge it. Dependabot will still automatically merge this pull request if you amend it and your tests pass. |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@nuxt/[email protected] |
🚨 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 install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. 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 [@nuxt/content](https://github.com/nuxt/content) from 2.12.0 to 2.12.1. - [Release notes](https://github.com/nuxt/content/releases) - [Changelog](https://github.com/nuxt/content/blob/main/CHANGELOG.md) - [Commits](nuxt/content@v2.12.0...v2.12.1) --- updated-dependencies: - dependency-name: "@nuxt/content" dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
b111514
to
4e8f7f1
Compare
Bumps @nuxt/content from 2.12.0 to 2.12.1.
Changelog
Sourced from
@nuxt/content
's changelog.Commits
b205a17
chore(release): release v2.12.12c68c3e
chore(deps): update all non-major dependencies (#2578)8a176f9
chore: upgrade@nuxtjs/mdc
2890b25
chore(deps): update dependency@nuxt/ui-pro
to v1 (#2571)9e82008
chore(deps): update all non-major dependencies (#2543)f3bfb05
chore: fix Nuxt extends in renovate.json (#2567)8f560c6
fix(types): add const type parameter for QueryBuilder.only() and .without() (...a0ab377
fix: splitgetContent
to chunks ingetIndexedContentsList
(#2354) (#2549)7966323
fix(types): use const type parameter for QueryBuilder only (#2546)233771b
chore(deps): update pnpm/action-setup action to v3 (#2550)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 will merge this PR once CI passes on it, as requested by @hougesen.
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)