Skip to content

Conversation

@aravindbuilt
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @preact/signals from 1.3.0 to 2.0.0.

ℹ️ 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 PR contains major version upgrade(s), and may be a breaking change.

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

  • The recommended version was released a month ago.

Release notes
Package name: @preact/signals
  • 2.0.0 - 2024-12-17

    Major Changes

    • #604 fea3e8d Thanks @ JoviDeCroock! - Defer all DOM updates by an animation frame, this should make it so
      that any previously synchronous DOM update will be instead delayed by an
      animation frame. This allows Preact to first perform its own render
      cycle and then our direct DOM updates to occur. These will now
      be performed in a batched way which is more performant as the browser
      is prepared to handle these during the animation frame.

      This does impact how Preact based signals are tested, when
      you perform a signal update, you'll need to wrap it in act. In a way
      this was always the case, as a signal update that resulted in
      a Preact state update would require it to be wrapped in act, but
      now this is the norm.

    Minor Changes

    Patch Changes

    • #609 8e6e2de Thanks @ JoviDeCroock! - Change timing to a double microtask so we are behind the Preact render queue but can't delay as much as a user-input coming in.
  • 1.3.2 - 2025-01-13

    Patch Changes

    • #641 e932cfc Thanks @ JoviDeCroock! - Change the way we deal with state settling hooks, when we know we are dealing with hooks that can settle their A -> B -> A state (and wind up at the same value). We should not verbatim rerender in our custom shouldComponentUpdate. Instead we should trust that hooks have handled their own state settling.
  • 1.3.1 - 2024-11-27

    Patch Changes

  • 1.3.0 - 2024-07-06
from @preact/signals GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • 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:

Snyk has created this PR to upgrade @preact/signals from 1.3.0 to 2.0.0.

See this package in npm:
@preact/signals

See this project in Snyk:
https://app.snyk.io/org/contentstack-ghost/project/aa5614b9-feb5-4b0b-bb14-d064efda2c51?utm_source=github&utm_medium=referral&page=upgrade-pr
@aravindbuilt aravindbuilt requested a review from a team as a code owner January 16, 2025 03:08
@csAyushDubey csAyushDubey requested review from a team as code owners December 21, 2025 12:02
Copy link
Contributor

@csAyushDubey csAyushDubey left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions
Copy link

github-actions bot commented Dec 21, 2025

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 71.47% 7971 / 11152
🔵 Statements 71.47% 7971 / 11152
🔵 Functions 74.52% 316 / 424
🔵 Branches 85.3% 1190 / 1395
File CoverageNo changed files found.
Generated in workflow #716 for commit 8b4b924 by the Vitest Coverage Report Action

Copy link
Contributor

@karancs06 karancs06 left a comment

Choose a reason for hiding this comment

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

Lgtm

@csAyushDubey csAyushDubey merged commit 8aee795 into main Dec 21, 2025
10 checks passed
@csAyushDubey csAyushDubey deleted the snyk-upgrade-cbbc723eccb80e86ea1b15455162206d branch December 21, 2025 15:45
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.

5 participants