Skip to content

Conversation

@X-oss-byte
Copy link
Owner

@X-oss-byte X-oss-byte commented Mar 23, 2025

snyk-top-banner

Snyk has created this PR to upgrade preact from 10.11.3 to 10.26.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.


  • The recommended version is 46 versions ahead of your current version.

  • The recommended version was released 23 days ago.

Release notes
Package name: preact
  • 10.26.4 - 2025-02-28

    Fixes

  • 10.26.3 - 2025-02-27

    Fixes

    Types

    Maintenance

  • 10.26.2 - 2025-02-18

    This is a hotfix release! If you are encountering bundling issues with regards to unallowed import syntax, this will fix it!

    Fixes

    Maintenance

  • 10.26.1 - 2025-02-18

    Fixes

    • Fixes memory leak when wrapping Fragment is captured by an effect closure (#4680, thanks @ JoviDeCroock)

    Optimization

    Maintenance

  • 10.26.0 - 2025-02-16

    Features

    Fixes

    Types

    Maintenance

  • 10.25.4 - 2024-12-28

    Types

    Fixes

  • 10.25.3 - 2024-12-18

    Fixes

    Types

    • Add default event target types for HTML attribute interfaces (#4606, thanks @ rschristian)
  • 10.25.2 - 2024-12-12

    Notable

    Revert unkeyed no-search (#4604, thanks @ JoviDeCroock)

    We noticed that there's a few unpleasant scenario's that could form from this change, we wanted to be on the safe side here and revert this for the time being. if you run into issues with swapping components placement wise in a list use the key property.

    Fixes

    • Add missing space in hydration mismatch message (#4602, thanks @ sirreal)

    Types

    • fix max and min type definition to allow number (#4598, thanks @ devlux)

    Performance

    Maintenance

  • 10.25.1 - 2024-12-02

    Fixes

    Types

    Maintenance

  • 10.25.0 - 2024-11-22

    Features

    Move per-element type interfaces into core and more strictly type IntrinsicElements (#4546, thanks @ rschristian)

    This adds per-element typings for every DOM-node type, this means that our types might become slightly stricter when you are using DOM attributes/properties where they are not allowed, an example of this might be <div src="x" />.

    If you notice any issues when upgrading tell us about them, we can evaluate whether we have missed a case.

    Recreate unkeyed functional components when they change position. (#4550, thanks @ JoviDeCroock)

    This is a long time bugfix, when we have elements that look like

    return (
    	{condition ? <Element /> : null}
    	{condition ? null : <Element />
    )

    We would reuse the state of the first VNode to render the second one when the condition switches. When you are using key, this issue was not present.

    Support { handleEvent() {} } object interface as a listener (#4538, thanks @ lilnasy)

    We've added support for attaching object/class event-handlers

    let handler = {
    onclick,
    handleEvent() {
    this.onclick()
    }
    }

    <div onClick={handler} />

    Fixes

    Maintenance

  • 10.24.3 - 2024-10-14
  • 10.24.2 - 2024-10-04
  • 10.24.1 - 2024-09-24
  • 10.24.0 - 2024-09-14
  • 10.23.2 - 2024-08-12
  • 10.23.1 - 2024-07-25
  • 10.23.0 - 2024-07-23
  • 10.22.1 - 2024-07-01
  • 10.22.0 - 2024-05-15
  • 10.21.0 - 2024-04-30
  • 10.20.2 - 2024-04-09
  • 10.20.1 - 2024-03-23
  • 10.20.0 - 2024-03-20
  • 10.19.7 - 2024-03-18
  • 10.19.6 - 2024-02-22
  • 10.19.5 - 2024-02-16
  • 10.19.4 - 2024-02-08
  • 10.19.3 - 2023-12-08
  • 10.19.2 - 2023-11-14
  • 10.19.1 - 2023-11-11
  • 10.19.0 - 2023-11-11
  • 10.18.2 - 2023-11-03
  • 10.18.1 - 2023-10-01
  • 10.18.0 - 2023-09-28
  • 10.17.1 - 2023-08-19
  • 10.17.0 - 2023-08-14
  • 10.16.0 - 2023-07-09
  • 10.15.1 - 2023-05-27
  • 10.15.0 - 2023-05-21
  • 10.14.1 - 2023-05-16
  • 10.14.0 - 2023-05-14
  • 10.13.2 - 2023-03-27
  • 10.13.1 - 2023-03-09
  • 10.13.0 - 2023-02-24
  • 10.12.1 - 2023-02-09
  • 10.12.0 - 2023-02-06
  • 10.11.3 - 2022-11-14
from preact GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Summary by Sourcery

Chores:

  • Update preact dependency to the latest version.

Snyk has created this PR to upgrade preact from 10.11.3 to 10.26.4.

See this package in npm:
preact

See this project in Snyk:
https://app.snyk.io/org/sammytezzy/project/d44a33bd-57c9-417a-aad9-c6257f92658a?utm_source=github&utm_medium=referral&page=upgrade-pr
@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@changeset-bot
Copy link

changeset-bot bot commented Mar 23, 2025

⚠️ No Changeset found

Latest commit: cd82765

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@sourcery-ai
Copy link

sourcery-ai bot commented Mar 23, 2025

Reviewer's Guide by Sourcery

This pull request upgrades the preact dependency from version 10.11.3 to 10.26.4 by modifying the version number in package.json.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
The pull request upgrades the preact dependency from version 10.11.3 to 10.26.4.
  • Updated the preact version in package.json.
packages/core/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

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.

3 participants