patch release

[KyleAMathews]

🎯 Changes

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm run test:pr.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Chores
  • Version bump for package maintenance.

[coderabbitai]

📝 Walkthrough

Walkthrough

The @tanstack/intent package version is incremented from 0.0.28 to 0.0.29 in the package manifest file.

Changes

Cohort / File(s)	Summary
Package Version Bump packages/intent/package.json	Version updated from 0.0.28 to 0.0.29 for @tanstack/intent package.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Possibly related PRs

• patch release #101: Also involves version bumps to the @tanstack/intent package manifest.

Poem

🐰 A hop, a skip, a version's rise,
From point-two-eight to point-two-nine,
The package gleams with updated pride,
Tiny tweaks make progress shine! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description follows the required template structure but the 'Changes' section is entirely empty. All checklist items remain unchecked, providing no confirmation of testing or changeset generation.	Complete the Changes section with details about the version bump, check off completed checklist items, and confirm a changeset was generated for the published package update.
Title check	❓ Inconclusive	The title 'patch release' is vague and generic. While it relates to the version bump in the changeset, it does not clearly communicate the specific change or which package is being updated.	Use a more specific title that identifies the package and change, such as 'Bump @tanstack/intent to 0.0.29' or 'Release @tanstack/intent 0.0.29'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 patch2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 5d91a5a

Command	Status	Duration	Result
nx affected --targets=test:eslint,test:sherif,t...	✅ Succeeded	5s	View ↗
nx run-many --targets=build --exclude=examples/**	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-03 15:13:13 UTC

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@tanstack/intent@108

commit: 5d91a5a

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/intent/package.json`:
- Line 3: The repo is missing a changeset for the version bump of package
"intent" to 0.0.29; create a new changeset file that lists the package "intent"
with a "patch" release in the changeset frontmatter and a one- or two-line
description of the change (e.g., "Patch release for bugfixes/updates"), so the
changelog can be generated; ensure the file uses the standard changeset
YAML/frontmatter format and includes "intent": patch and mentions version 0.0.29
in the description.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d3abbacb-9954-400d-b85a-ff3e035a5e6c

📥 Commits

Reviewing files that changed from the base of the PR and between 85fb1c7 and 5d91a5a.

📒 Files selected for processing (1)

• packages/intent/package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check for changeset files in the .changeset directory

# List all changeset files (excluding README)
fd -e md . .changeset --exclude README.md --exec echo "Found changeset: {}"

# If no changesets found, this might be intentional for a manual release
if [ -z "$(fd -e md . .changeset --exclude README.md)" ]; then
  echo "No changeset files found in .changeset directory"
  echo "Checking if .changeset directory exists..."
  if [ -d ".changeset" ]; then
    echo ".changeset directory exists"
    ls -la .changeset/
  else
    echo "No .changeset directory found - project may not use changesets"
  fi
fi

Repository: TanStack/intent

Length of output: 350

---

🏁 Script executed:

# Check for release/contribution guidelines
fd -i 'contributing\|changelog\|release' --type f --max-results 20

Repository: TanStack/intent

Length of output: 41

---

🏁 Script executed:

# Check .changeset/config.json to see if changesets are required
cat .changeset/config.json

Repository: TanStack/intent

Length of output: 506

---

🏁 Script executed:

# Look at recent git history for other version bumps and changesets
git log --oneline -20 -- packages/intent/package.json

Repository: TanStack/intent

Length of output: 80

---

🏁 Script executed:

# Check if there are any CI workflows that validate changesets
fd 'workflow\|\.yml\|\.yaml' . .github --type f | head -20

Repository: TanStack/intent

Length of output: 41

---

Add a changeset file for this version bump.

This project uses changesets for release management (see .changeset/config.json), but no changeset file is included in this PR. The changelog is automatically generated from changesets using the GitHub Compact formatter. Without a changeset, the release notes and changelog will be incomplete.

Add a changeset file describing this patch release to .changeset/ before merging.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/intent/package.json` at line 3, The repo is missing a changeset for
the version bump of package "intent" to 0.0.29; create a new changeset file that
lists the package "intent" with a "patch" release in the changeset frontmatter
and a one- or two-line description of the change (e.g., "Patch release for
bugfixes/updates"), so the changelog can be generated; ensure the file uses the
standard changeset YAML/frontmatter format and includes "intent": patch and
mentions version 0.0.29 in the description.