Update dependency @tanstack/react-form to v1.33.0 by amitsingh-007 · Pull Request #4021 · amitsingh-007/bypass-links

This PR bumps @tanstack/react-form from 1.29.1 to 1.33.0 in the pnpm workspace catalog, with corresponding lockfile updates for the transitive dependencies @tanstack/form-core, @tanstack/react-store, and @tanstack/store.

The version range spans four minor releases; release notes show no breaking changes — only a bug fix for array re-rendering (v1.32.0) and the new FormGroup API (v1.33.0).
Two pre-existing transitive packages (stream-to-promise@2.2.0 and tsconfck@3.1.6) now surface deprecated annotations in the lockfile; these are not introduced by this PR but may be worth tracking separately.

Confidence Score: 5/5

Routine dependency bump with no breaking changes across the four intermediate releases; only lockfile and workspace catalog are touched.

All changes are confined to the pnpm lockfile and workspace catalog. The intermediate release notes document only additive features and bug fixes, with no API removals that would affect existing form usage in the repo.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Update dependency @tanstack/react-form t..." | Re-trigger Greptile}

qodo-code-review · 2026-07-08T16:26:59Z

PR Summary by Qodo

Bump @tanstack/react-form to v1.33.0 (pnpm catalog)

⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Update the workspace catalog to use @tanstack/react-form v1.33.0.
• Refresh pnpm lockfile to reflect updated TanStack transitive dependencies.
• Record new deprecation metadata surfaced during lockfile re-resolution.

Diagram

graph TD
  WS[/"pnpm-workspace.yaml"/] --> LOCK[/"pnpm-lock.yaml"/] --> RF["@tanstack/react-form 1.33.0"] --> APP["React app"]
  RF --> CORE["@tanstack/form-core 1.33.0"] --> STORE["@tanstack/store 0.11.0"]
  RF --> RSTORE["@tanstack/react-store 0.11.0"] --> STORE
  subgraph Legend
    direction LR
    _doc[/"YAML file"/] ~~~ _pkg["Package version"] ~~~ _app["App"]
  end

High-Level Assessment

This is the standard/expected approach for a Renovate-driven pnpm-catalog upgrade. Main reviewer focus should be on confirming no breaking changes are introduced for existing forms (optional adoption of the new FormGroup API can be deferred) and ensuring CI/UI smoke tests cover key form flows.

Files changed (2) +22 / -20

Other (2) +22 / -20

pnpm-lock.yamlResolve @tanstack/react-form 1.33.0 and transitive TanStack upgrades +21/-19

Resolve @tanstack/react-form 1.33.0 and transitive TanStack upgrades

• Updates the lockfile entries to @tanstack/react-form@1.33.0 and aligns transitive TanStack packages (notably @tanstack/form-core, @tanstack/react-store, and @tanstack/store). Also captures newly surfaced deprecation metadata for some resolved packages during lockfile regeneration.

pnpm-lock.yaml

pnpm-workspace.yamlBump workspace catalog pin for @tanstack/react-form to 1.33.0 +1/-1

Bump workspace catalog pin for @tanstack/react-form to 1.33.0
• Updates the pnpm workspace catalog version for @tanstack/react-form from 1.29.1 to 1.33.0 so all importers resolve the newer version.
pnpm-workspace.yaml

qodo-code-review · 2026-07-08T16:29:32Z

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0) 📜 Skill insights (0)

Context used

✅ Tickets: 🎫 Dont close Google Web Activity tab on logout if watch time was >1hour

✅ Compliance rules (platform): 22 rules

✅ Skills: e2e-test-generation

1. Deprecated stream-to-promise 🐞 Bug ⚙ Maintainability

Description

pnpm-lock.yaml now records stream-to-promise@2.2.0 as deprecated, and it is present in the
dependency graph via @vercel/fun. This is a tooling/dependency health risk (reduced
maintenance/support) rather than an immediate functional bug.

Code

pnpm-lock.yaml[R6676-6678]

  stream-to-promise@2.2.0:
    resolution: {integrity: sha512-HAGUASw8NT0k8JvIVutB2Y/9iBk7gpgEyAudXwNJmZERdMITGdajOa4VJfD/kNiA3TppQpTP4J+CtcHwdzKBAw==}
+    deprecated: Deprecated. Use node:stream/promises and node:stream/consumers instead.

Relevance

⭐ Low
Lockfile deprecation-based upgrade suggestions were rejected previously (pnpm-lock.yaml deprecation
notices) in PR #3812.
PR-#3812

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The lockfile explicitly marks stream-to-promise@2.2.0 as deprecated and also shows it as a
dependency of @vercel/fun@1.3.0, demonstrating it is still in the resolved dependency graph.

pnpm-lock.yaml[6676-6679]
pnpm-lock.yaml[9789-9804]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`stream-to-promise@2.2.0` is marked as deprecated in `pnpm-lock.yaml` and is pulled in transitively (currently via `@vercel/fun`). While not an immediate runtime failure, deprecated packages are higher-risk to keep long-term.

## Issue Context
The lockfile shows:
- `stream-to-promise@2.2.0` with a `deprecated:` message
- `@vercel/fun@1.3.0` depending on `stream-to-promise: 2.2.0`

## Fix Focus Areas
- pnpm-lock.yaml[6676-6683]
- pnpm-lock.yaml[9789-9804]

## What to change
- Prefer upgrading the top-level dependency that brings in `@vercel/fun` (or upgrading `@vercel/fun` itself if it is a direct dependency) to a version that no longer depends on `stream-to-promise`.
- If no upgrade path exists, document/accept the transitive dependency risk (e.g., via internal dependency health tracking).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Unmaintained tsconfck 🐞 Bug ⚙ Maintainability

Description

pnpm-lock.yaml now records tsconfck@3.1.6 as unmaintained and it is pulled in by
vite-tsconfig-paths. This increases maintenance risk for the build/tooling dependency chain
(unmaintained packages are less likely to receive compatibility fixes).

Code

pnpm-lock.yaml[R6943-6946]

  tsconfck@3.1.6:
    resolution: {integrity: sha512-ks6Vjr/jEw0P1gmOVwutM3B7fWxoWBL2KRDb1JfqGVawBmO5UsvmWOQFGHBPl5yxYz4eERr19E6L7NMv+Fej4w==}
    engines: {node: ^18 || >=20}
+    deprecated: unmaintained

Relevance

⭐ Low
Team previously rejected acting on pnpm-lock.yaml deprecation notices/transitive upgrades (PR
#3812); likely same for tsconfck unmaintained.
PR-#3812

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The lockfile explicitly labels tsconfck@3.1.6 as unmaintained and separately lists
vite-tsconfig-paths depending on that exact tsconfck version, proving the transitive relationship.

pnpm-lock.yaml[6943-6947]
pnpm-lock.yaml[14471-14476]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`tsconfck@3.1.6` is marked as `deprecated: unmaintained` in the lockfile and is used transitively via `vite-tsconfig-paths`.

## Issue Context
The lockfile shows:
- `tsconfck@3.1.6` with `deprecated: unmaintained`
- `vite-tsconfig-paths@6.1.1` depending on `tsconfck: 3.1.6(...)`

## Fix Focus Areas
- pnpm-lock.yaml[6943-6948]
- pnpm-lock.yaml[14471-14476]

## What to change
- Prefer upgrading `vite-tsconfig-paths` (or the top-level dependency that pulls it in) to a version that removes/replaces `tsconfck`.
- If it cannot be removed, explicitly accept the risk and monitor for tooling issues during future Vite/TypeScript upgrades.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Update dependency @tanstack/react-form to v1.33.0

540eebd

amitsingh-007 enabled auto-merge (squash) July 8, 2026 16:26

amitsingh-007 merged commit 25c3365 into renovate-updates Jul 8, 2026
1 check passed

amitsingh-007 deleted the renovate/tanstack-form-monorepo branch July 8, 2026 16:26

Navigation Menu

Repository navigation

Update dependency @tanstack/react-form to v1.33.0 - #4021

Update dependency @tanstack/react-form to v1.33.0#4021
amitsingh-007 merged 1 commit into
renovate-updatesfrom
renovate/tanstack-form-monorepo

amitsingh-007 commented Jul 8, 2026 •

edited by greptile-apps Bot

Loading

Uh oh!

Uh oh!

qodo-code-review Bot commented Jul 8, 2026

Uh oh!

qodo-code-review Bot commented Jul 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

amitsingh-007 commented Jul 8, 2026 • edited by greptile-apps Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v1.33.0

Minor Changes

Patch Changes

v1.32.1

Patch Changes

v1.32.0

Patch Changes

v1.31.0

Patch Changes

v1.30.0

Patch Changes

v1.29.3

Patch Changes

v1.29.2

Patch Changes

Configuration

Greptile Summary

Confidence Score: 5/5

Uh oh!

Uh oh!

qodo-code-review Bot commented Jul 8, 2026

PR Summary by Qodo

Uh oh!

qodo-code-review Bot commented Jul 8, 2026

Code Review by Qodo

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

amitsingh-007 commented Jul 8, 2026 •

edited by greptile-apps Bot

Loading

`v1.33.0`

`v1.32.1`

`v1.32.0`

`v1.31.0`

`v1.30.0`

`v1.29.3`

`v1.29.2`