chore(deps): lock file maintenance by renovate[bot] · Pull Request #315 · TanStack/store · GitHub
Skip to content

chore(deps): lock file maintenance - #315

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#315
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented May 1, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

Summary by CodeRabbit

  • Documentation
    • Updated reference paths in framework documentation.

@renovate renovate Bot added the dependencies label May 1, 2026
@coderabbitai

coderabbitai Bot commented May 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 307498df-d242-4c8f-ba2f-6a1a43943066

📥 Commits

Reviewing files that changed from the base of the PR and between 83e2978 and f3bb2d8.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • docs/framework/angular/reference/interfaces/InjectSelectorOptions.md
📝 Walkthrough

Walkthrough

A documentation reference is updated in the Angular interface documentation, changing a version reference from Angular 21.2.8 to Angular 21.2.11 in a "Defined in" metadata field. No code or functional changes.

Changes

Cohort / File(s) Summary
Documentation Reference Update
docs/framework/angular/reference/interfaces/InjectSelectorOptions.md		 Updated Angular version reference in the "Defined in" field from 21.2.8 to 21.2.11 for the debugName? property.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version number hops along,
From 21.2.8, not quite so strong,
To 21.2.11, shiny and new,
In the docs where the references grew! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description explains the lock file maintenance performed by Renovate but does not follow the repository's required template structure with sections for 'Changes' and 'Checklist'. Restructure the description to match the template: add a '🎯 Changes' section summarizing the update, include the '✅ Checklist' with the two required items, and specify '🚀 Release Impact' (likely 'dev-only' since locks don't affect published code).
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore(deps): lock file maintenance' accurately describes the primary change—a lock file update by Renovate—and follows conventional commit format.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/lock-file-maintenance

Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

Comment @coderabbitai help to get the list of available commands and usage tips.

@nx-cloud

nx-cloud Bot commented May 1, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

To disable these notifications, a workspace admin can disable them in workspace settings.

View your CI Pipeline Execution ↗ for commit e4cdb3f

Command Status Duration Result
nx affected --targets=test:sherif,test:knip,tes... ❌ Failed 58s View ↗
nx run-many --target=build --exclude=examples/** ✅ Succeeded 1s View ↗

☁️ Nx Cloud last updated this comment at 2026-05-01 00:49:13 UTC

@github-actions

github-actions Bot commented May 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🚀 Changeset Version Preview

No changeset entries found. Merging this PR will not cause a version bump for any packages.

@pkg-pr-new

pkg-pr-new Bot commented May 1, 2026 •
edited
Loading

Copy link
Copy Markdown
@tanstack/angular-store

npm i https://pkg.pr.new/@tanstack/angular-store@315

@tanstack/preact-store

npm i https://pkg.pr.new/@tanstack/preact-store@315

@tanstack/react-store

npm i https://pkg.pr.new/@tanstack/react-store@315

@tanstack/solid-store

npm i https://pkg.pr.new/@tanstack/solid-store@315

@tanstack/store

npm i https://pkg.pr.new/@tanstack/store@315

@tanstack/svelte-store

npm i https://pkg.pr.new/@tanstack/svelte-store@315

@tanstack/vue-store

npm i https://pkg.pr.new/@tanstack/vue-store@315

commit: f3bb2d8

@renovate

renovate Bot commented May 1, 2026

Copy link
Copy Markdown
Contributor Author

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

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants