chore(deps): Update dependency @astrojs/prism to v3

[neolitec]

This PR contains the following updates:

Package	Type	Update	Change
@astrojs/prism (source)	dependencies	major	^2.0.0 -> ^3.0.0

---

Release Notes

withastro/astro

v3.1.0

Compare Source

Minor Changes

• #​10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

v3.0.0

Compare Source

Major Changes

• #​8188 d0679a666 Thanks @​ematipico! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

• #​8179 6011d52d3 Thanks @​matthewp! - Astro 3.0 Release Candidate

v2.1.2

Compare Source

Patch Changes

• #​7104 826e02890 Thanks @​bluwy! - Specify "files" field to only publish necessary files

v2.1.1

Compare Source

Patch Changes

• #​6494 a13e9d7e3 Thanks @​Yan-Thomas! - Consistency improvements to several package descriptions

v2.1.0

Compare Source

Minor Changes

• #​6213 afbbc4d5b Thanks @​Princesseuh! - Updated compilation settings to disable downlevelling for Node 14

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/[email protected]	Did you mean: **number-**is-nan	docs/yarn.lock	⚠︎
Possible typosquat attack	npm/[email protected]	Did you mean: array-unique	docs/yarn.lock	⚠︎
Critical CVE	npm/@babel/[email protected]	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2	docs/yarn.lock	⚠︎
Possible typosquat attack	npm/[email protected]	Did you mean: html-escaper-html	docs/yarn.lock	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/[email protected]

[socket-security]

Report too large to display inline

View full report↗︎