Skip to content
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

[Snyk] Upgrade @astrojs/node from 3.1.0 to 8.3.4 #1030

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

q1blue
Copy link
Collaborator

@q1blue q1blue commented Oct 13, 2024

Snyk has created this PR to upgrade @astrojs/node from 3.1.0 to 8.3.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 51 versions ahead of your current version.
  • The recommended version was released 24 days ago, on 2024-09-20.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
159/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00152, Social Trends: No, Days since published: 481, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.64, Score Version: V5
Proof of Concept
Cross-site Scripting
SNYK-JS-SEND-7926862
159/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00152, Social Trends: No, Days since published: 481, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.64, Score Version: V5
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: @astrojs/node
  • 8.3.4 - 2024-09-20

    Patch Changes

  • 8.3.3 - 2024-08-14
  • 8.3.2 - 2024-06-24
  • 8.3.1 - 2024-06-17
  • 8.3.0 - 2024-06-11
  • 8.2.6 - 2024-06-08
  • 8.2.5 - 2024-03-20
  • 8.2.4 - 2024-03-18
  • 8.2.3 - 2024-03-01
  • 8.2.2 - 2024-03-01
  • 8.2.1 - 2024-02-23
  • 8.2.0 - 2024-02-01
  • 8.1.0 - 2024-01-26
  • 8.0.0 - 2024-01-18
  • 7.0.4 - 2024-01-02
  • 7.0.3 - 2023-12-27
  • 7.0.2 - 2023-12-20
  • 7.0.1 - 2023-12-11
  • 7.0.0 - 2023-12-05
  • 7.0.0-beta.1 - 2023-11-29
  • 7.0.0-beta.0 - 2023-11-27
  • 6.1.0 - 2023-11-28
  • 6.0.4 - 2023-11-16
  • 6.0.3 - 2023-10-05
  • 6.0.2 - 2023-10-02
  • 6.0.1 - 2023-09-21
  • 6.0.0 - 2023-08-30
  • 6.0.0-rc.1 - 2023-08-22
  • 6.0.0-beta.0 - 2023-08-03

    Major Changes

    • #367 e02b54a Thanks @ alexanderniebuhr! - Removed support for the Squoosh image service. As the underlying library libsquoosh is no longer maintained, and the image service sees very little usage we have decided to remove it from Astro.

      Our recommendation is to use the base Sharp image service, which is more powerful, faster, and more actively maintained.

      - import { squooshImageService } from "astro/config";
      import { defineConfig } from "astro/config";

    export default defineConfig({
    - image: {
    - service: squooshImageService()
    - }
    });

    If you are using this service, and cannot migrate to the base Sharp image service, a third-party extraction of the previous service is available here: https://github.com/Princesseuh/astro-image-service-squoosh

  • #367 e02b54a Thanks @ alexanderniebuhr! - Deprecates the functionPerRoute option

    This option is now deprecated, and will be removed entirely in Astro v5.0. We suggest removing this option from your configuration as soon as you are able to:

    - functionPerRoute: true,
    }),
    });

  • #375 e7881f7 Thanks @ Princesseuh! - Updates internal code to works with Astro 5 changes to hybrid rendering. No changes are necessary to your project, apart from using Astro 5

  • #397 776a266 Thanks @ Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

    Starting from this release, no breaking changes will be introduced unless absolutely necessary.

    To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

  • #392 3a49eb7 Thanks @ Princesseuh! - Updates internal code for Astro 5 changes. No changes is required to your project, apart from using Astro 5

Minor Changes

  • 5.3.6 - 2023-08-23
  • 5.3.5 - 2023-08-18
  • 5.3.4 - 2023-08-15
  • 5.3.3 - 2023-08-11
  • 5.3.2 - 2023-08-03
  • 5.3.1 - 2023-08-01
  • 5.3.0 - 2023-06-22
  • 5.2.0 - 2023-06-06
  • 5.1.4 - 2023-05-18
  • 5.1.3 - 2023-05-12
  • 5.1.2 - 2023-05-01
  • 5.1.1 - 2023-04-05
  • 5.1.0 - 2023-03-07
  • 5.0.4 - 2023-02-23
  • 5.0.3 - 2023-02-03
  • 5.0.2 - 2023-02-01
  • 5.0.1 - 2023-01-26
  • 5.0.0 - 2023-01-24
  • 5.0.0-beta.1 - 2023-01-12
  • 5.0.0-beta.0 - 2023-01-03
  • 4.0.0 - 2022-12-16
  • 3.1.1 - 2022-12-12
  • 3.1.0 - 2022-11-17
  • from @astrojs/node GitHub release notes

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

    For more information:

    🧐 View latest project report

    🛠 Adjust upgrade PR settings

    🔕 Ignore this dependency or unsubscribe from future upgrade PRs

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants