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 jotai from 1.3.0 to 1.6.5 #275

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

Conversation

NOUIY
Copy link
Owner

@NOUIY NOUIY commented May 20, 2022

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade jotai from 1.3.0 to 1.6.5.

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 29 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2022-04-28.
Release notes
Package name: jotai
  • 1.6.5 - 2022-04-28

    This reverts #1089 which was introduced in v1.6.3, which can behave buggy in some cases.

    What's Changed

    • fix(core): resolve infinite loop with loadable of derived async atom in some cases by @ riemonyamada in #1118

    New Contributors

    Full Changelog: v1.6.4...v1.6.5

  • 1.6.4 - 2022-04-15

    ⚠️ Please use v1.6.5 and above.


    This release contains several small improvements in non-core functions. Some of changes introduce deprecation of simple form, which will be warned.

    What's Changed

    • feat(devtools): enabled option in useAtomDevtools by @ Aslemammad in #1095
    • feat(devtools): enabled option useAtomsDevtools by @ Aslemammad in #1076
    • feat(utils): splitAtom actions for remove/insert/move by @ dai-shi in #1097
    • fix(core,utils): improve awaited types and waitForAll type by @ dai-shi in #1098
    • fix(utils): make useAtomCallback return sync if possible by @ dai-shi in #1101

    Full Changelog: v1.6.3...v1.6.4

  • 1.6.3 - 2022-04-09

    ⚠️ Please use v1.6.5 and above.


    There was a regression in atomWithStorage in v1.6.2, and it's fixed.

    What's Changed

    • fix(utils): undefined bug with no entry in storage by @ dai-shi in #1088
    • fix(core): handle returning infinite promise in derived atoms by @ dai-shi in #1089

    Full Changelog: v1.6.2...v1.6.3

  • 1.6.2 - 2022-04-05

    This improves atomWithObservable and fixes some hypothetical issues.

    What's Changed

    • fix(utils/atomWithStorage): handle edge case of value inconsistency with subscription by @ dai-shi in #1080
    • fix(core,urql): useDebugState and some envvar handling by @ dai-shi in #1070
    • fix(utils): Initial data for atomWithObservable by @ 11bit in #1058

    New Contributors

    Full Changelog: v1.6.1...v1.6.2

  • 1.6.1 - 2022-03-09

    This includes some small fixes and improvements.

    What's Changed

    • fix(utils): atomWithObservable is not resubscribed after remount by @ 11bit in #1016
    • fix(devtools): better types with official devtools extension types by @ Aslemammad in #1049
    • fix(devtools): Add support for debugLabels for atom utils by @ Thisen in #1051

    New Contributors

    Full Changelog: v1.6.0...v1.6.1

  • 1.6.0 - 2022-02-11

    This release includes a long-awaited feature unstable_createStore. Although it's an experimental feature, it opens up possibilities for more use cases. Please feel free to experiment with it. Another change is to have useAtomValue and useSetAtom in core, which is just additional APIs, and we keep previous APIs in jotai/utils. UMD/SystemJS bundles are improved. See details below.

    What's Changed

    • breaking(core,utils): remove some deprecated features by @ dai-shi in #979
    • feat(build): use __DEV__ to control development mode by @ dai-shi in #968
    • feat(core): unstable_createStore by @ dai-shi in #922
    • feat(utils/atomWithStorage): Add subscribe to storage events in defaultStorage by @ Thisen in #1004
    • feat(core): Move useAtomValue and useSetAtom to core by @ Thisen in #989

    New Contributors

    Full Changelog: v1.5.3...v1.6.0

  • 1.5.3 - 2022-01-18
    Read more
  • 1.5.2 - 2022-01-12

    v1.5.1 has an issue accidentally in non-browser environment like Next.js and React Native. This should fix it.

    What's Changed

    • fix(utils): atomWithStorage should deal with no localStorage by @ dai-shi in #951
    • fix(babel): Require that atom is in module scope for react refresh by @ Thisen in #952

    Full Changelog: v1.5.1...v1.5.2

  • 1.5.1 - 2022-01-11
    Read more
  • 1.5.0 - 2021-12-30
    Read more
  • 1.4.9 - 2021-12-20
  • 1.4.8 - 2021-12-16
  • 1.4.7 - 2021-12-08
  • 1.4.6 - 2021-11-30
  • 1.4.5 - 2021-11-24
  • 1.4.4 - 2021-11-19
  • 1.4.3 - 2021-11-07
  • 1.4.2 - 2021-10-25
  • 1.4.1 - 2021-10-23
  • 1.4.0 - 2021-10-14
  • 1.3.9 - 2021-10-10
  • 1.3.8 - 2021-10-07
  • 1.3.7 - 2021-10-01
  • 1.3.6 - 2021-09-24
  • 1.3.5 - 2021-09-17
  • 1.3.4 - 2021-09-13
  • 1.3.3 - 2021-09-09
  • 1.3.2 - 2021-08-27
  • 1.3.1 - 2021-08-25
  • 1.3.0 - 2021-08-10
from jotai 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