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 react-sweet-state from 2.5.1 to 2.5.2 #102

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

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade react-sweet-state from 2.5.1 to 2.5.2.

merge advice
ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 9 months ago, on 2021-02-03.
Release notes
Package name: react-sweet-state
  • 2.5.2 - 2021-02-03

    Bug fixes

    • Change batch implementation to not schedule if we are already inside a batched scheduled update

    Other changes

    • Published files are no longer transpiled to support IE11. RSS babel config now supports Edge 18+. But IE11 support can still be achieved by having consumers babel config transpile node_modules (or RSS specifically)
  • 2.5.1 - 2020-12-09

    Bug fixes

    • Ensure selectors returning arrays are shallow-equal checked, so mapping same elements (eg when using a normalised state) will not trigger a re-render
from react-sweet-state GitHub release notes
Commit messages
Package name: react-sweet-state

Compare


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

@atlassian-cla-bot
Copy link

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌snyk-bot

Already signed the CLA? To re-check, try refreshing the page.

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.

1 participant