Skip to content

⬆️ Update dependency @tanstack/store to ^0.11.0#1004

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/tanstack-store-0.x
Open

⬆️ Update dependency @tanstack/store to ^0.11.0#1004
renovate[bot] wants to merge 1 commit intomainfrom
renovate/tanstack-store-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 18, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tanstack/store (source) ^0.8.0^0.11.0 age adoption passing confidence

Release Notes

TanStack/store (@​tanstack/store)

v0.11.0

Compare Source

Minor Changes
  • Hooks included in this release: (#​306)
    • useAtom
    • useSelector
    • useStore (deprecated, replaced by useSelector)
    • createStoreContext (provides StoreProvider and useStoreContext for context-based consumption)

v0.10.0

Compare Source

Minor Changes
  • chore: update deps and change build process to tsdown (#​304)

v0.9.3

Compare Source

Patch Changes
  • Improve tree-shaking of alien-signals (#​297)

v0.9.2

Compare Source

Patch Changes
  • Fix a regression where mutable atoms could be updated internally with no updater and have their snapshot replaced with undefined. (#​289)

    Mutable atoms now ignore internal no-argument _update() calls, while computed atoms keep existing recomputation behavior. This prevents external-store state from disappearing during reactive graph cleanup.

v0.9.1

Compare Source

Patch Changes
  • derived createStore now returns readonly store (#​278)

v0.9.0

Compare Source

Minor Changes
  • Breaking changes (#​265)

    • new Store() is now createStore()
    • new Derived() is now a derived createStore():
      const derived = createStore(() => store.state * 2)
    • new Effect() removed in favor of store.subscribe():
      const { unsubscribe } = store.subscribe(() => {
        console.log(store.state)
      })
    • Uses alien-signals under the hood for efficient reactivity

Configuration

📅 Schedule: (in timezone Europe/Amsterdam)

  • Branch creation
    • "before 6am every weekday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added dependencies Upgrade or downgrade of project dependencies. javascript This PR is related to JavaScript. labels Feb 18, 2026
@renovate renovate Bot force-pushed the renovate/tanstack-store-0.x branch 16 times, most recently from 4053483 to 0e8d49c Compare February 26, 2026 07:40
@renovate renovate Bot force-pushed the renovate/tanstack-store-0.x branch 10 times, most recently from a290b28 to 912cd4f Compare March 6, 2026 08:43
@renovate renovate Bot force-pushed the renovate/tanstack-store-0.x branch 19 times, most recently from fa54b9a to 1dee082 Compare March 24, 2026 12:47
@renovate renovate Bot force-pushed the renovate/tanstack-store-0.x branch 9 times, most recently from 4f108fc to 1918e56 Compare March 31, 2026 08:15
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 10, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: undefined@undefined
npm error Found: @eslint/js@9.39.4
npm error node_modules/@eslint/js
npm error   dev @eslint/js@"^10.0.0" from the root project
npm error   @eslint/js@"9.39.4" from eslint@9.39.4
npm error   node_modules/eslint
npm error     dev eslint@"^10.0.0" from the root project
npm error     peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.1
npm error     node_modules/@eslint-community/eslint-utils
npm error       @eslint-community/eslint-utils@"^4.9.1" from @typescript-eslint/utils@8.58.1
npm error       node_modules/@typescript-eslint/utils
npm error         @typescript-eslint/utils@"8.58.1" from @typescript-eslint/eslint-plugin@8.58.1
npm error         node_modules/@typescript-eslint/eslint-plugin
npm error         2 more (@typescript-eslint/type-utils, typescript-eslint)
npm error       1 more (eslint)
npm error     8 more (@typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error dev @eslint/js@"^10.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@10.2.1
npm error node_modules/eslint
npm error   peerOptional eslint@"^10.0.0" from @eslint/js@10.0.1
npm error   node_modules/@eslint/js
npm error     dev @eslint/js@"^10.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-29T19_08_51_251Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-29T19_08_51_251Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Upgrade or downgrade of project dependencies. javascript This PR is related to JavaScript.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants