Bump @preact/signals-react from 1.3.4 to 2.2.0

[dependabot[bot]]

Bumps @preact/signals-react from 1.3.4 to 2.2.0.

Release notes

Sourced from @​preact/signals-react's releases.

@​preact/signals-react@​2.2.0

Minor Changes

• #591 e1a1465 Thanks @​JoviDeCroock! - Bump to support ReadonlySignal in jsx

@​preact/signals-react@​2.1.0

Minor Changes

• #578 931404e Thanks @​JoviDeCroock! - Allow for passing no argument to the signal and the type to be automatically inferred as T | undefined

Patch Changes

• #577 5a02bfa Thanks @​JoviDeCroock! - Throw an error when auto-tracking is used with React 19

• Updated dependencies [931404e]:

  • @​preact/signals-core@​1.7.0

@​preact/signals-react@​2.0.2

Patch Changes

• #570 d653451 Thanks @​developit! - Fix out-of-order effect error when suspending in React Native

• Updated dependencies [c8c95ac]:

  • @​preact/signals-core@​1.6.1

@​preact/signals-react@​2.0.1

Patch Changes

• #535 58befba Thanks @​jviide! - Publish packages with provenance statements

• Updated dependencies [d846def, cb6bdab, d846def, d846def, d846def]:

  • @​preact/signals-core@​1.6.0

@​preact/signals-react@​2.0.0

2.0.0

Major Changes

• #467 d7f43ef Thanks @​andrewiggins! - Remove auto tracking using React internals from signals-react package

  Before this change, importing @preact/signals-react would invoke side effects that hook into React internals to automatically track signals. This change removes those side effects and requires consumers to update their code to continue using signals in React.

  We made this breaking change because the mechanism we were using to automatically track signals was fragile and not reliable. We've had multiple issues reported where signals were not being tracked correctly. It would also lead to unexpected errors that were hard to debug.

  For some consumers and apps though, the current mechanism does work. If you'd like to continue using this mechanism, simply add import "@preact/signals/auto"; to the root of your app where you call ReactDOM.render. For our newly supported ways of using signals in React, check out the new Readme for @preact/signals-react.

@​preact/signals-react@​1.3.8

1.3.8

Patch Changes

... (truncated)

Changelog

Sourced from @​preact/signals-react's changelog.

2.2.0

Minor Changes

• #591 e1a1465 Thanks @​JoviDeCroock! - Bump to support ReadonlySignal in jsx

2.1.0

Minor Changes

• #578 931404e Thanks @​JoviDeCroock! - Allow for passing no argument to the signal and the type to be automatically inferred as T | undefined

Patch Changes

• #577 5a02bfa Thanks @​JoviDeCroock! - Throw an error when auto-tracking is used with React 19

• Updated dependencies [931404e]:

  • @​preact/signals-core@​1.7.0

2.0.2

Patch Changes

• #570 d653451 Thanks @​developit! - Fix out-of-order effect error when suspending in React Native

• Updated dependencies [c8c95ac]:

  • @​preact/signals-core@​1.6.1

2.0.1

Patch Changes

• #535 58befba Thanks @​jviide! - Publish packages with provenance statements

• Updated dependencies [d846def, cb6bdab, d846def, d846def, d846def]:

  • @​preact/signals-core@​1.6.0

2.0.0

Major Changes

• #467 d7f43ef Thanks @​andrewiggins! - Remove auto tracking using React internals from signals-react package

  Before this change, importing @preact/signals-react would invoke side effects that hook into React internals to automatically track signals. This change removes those side effects and requires consumers to update their code to continue using signals in React.

  We made this breaking change because the mechanism we were using to automatically track signals was fragile and not reliable. We've had multiple issues reported where signals were not being tracked correctly. It would also lead to unexpected errors that were hard to debug.

  For some consumers and apps though, the current mechanism does work. If you'd like to continue using this mechanism, simply add import "@preact/signals/auto"; to the root of your app where you call ReactDOM.render. For our newly supported ways of using signals in React, check out the new Readme for @preact/signals-react.

1.3.8

... (truncated)

Commits

• e046714 Version Packages (#592)
• cd9efbb Adjust ReadOnlySignal so we cant widen the type (#587)
• 26d49bf Version Packages (#579)
• 931404e chore(signals): add default undefined type (#578)
• 5a02bfa chore(signals-react): throw error when auto-tracking with React 19 (#577)
• 95b3747 Version Packages
• 6d049c1 fix suspense tests in react 16
• 1203c32 silence act() warnings in react 16
• 7a399a6 fix prod test act timing
• 9073ef4 remove describe.only
• Additional commits viewable in compare view

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 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)

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 70622a44be40e7421af649b0ad4733c80be65944

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[netlify[bot]]

❌ Deploy Preview for preact-signals failed.

Name	Link
🔨 Latest commit	70622a44be40e7421af649b0ad4733c80be65944
🔍 Latest deploy log	https://app.netlify.com/sites/preact-signals/deploys/66d20b554273ab000861db69

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.