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
  • Updated package version to 0.0.27.

[coderabbitai]

📝 Walkthrough

Walkthrough

The @tanstack/intent npm package version was incremented from 0.0.26 to 0.0.27. This is a routine version bump with no functional changes, dependency modifications, or alterations to the exported entry points or build configuration.

Changes

Cohort / File(s)	Summary
Package Version Bump packages/intent/package.json	Version incremented from 0.0.26 to 0.0.27.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A version bumped, a tiny hop,
From point-two-six, the rabbits stop,
To celebrate the climb so small,
Point-two-seven answers the call! 🎉

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description uses the required template structure but the critical 'Changes' section is completely empty with no explanation of what was changed or why.	Fill in the 'Changes' section with a description of what was modified and the motivation for this patch release.
Title check	❓ Inconclusive	The title 'patch release' is vague and generic, using non-descriptive terminology that doesn't convey the specific change being made.	Replace with a more descriptive title that specifies the actual change, such as 'Bump @tanstack/intent to 0.0.27' or 'Release @tanstack/intent v0.0.27'.

✅ 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 release

---

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 d798485

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

---

☁️ Nx Cloud last updated this comment at 2026-03-29 16:04:42 UTC

[pkg-pr-new]

Open in StackBlitz

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

commit: d798485

[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 package.json version was bumped directly to "0.0.27" without a
corresponding changeset; create a new changeset file in the .changeset directory
(or run the changeset CLI) that declares a patch release for the intent package
and includes a short summary of the changes, then run changeset version to
regenerate package.json and update CHANGELOG.md so the version and changelog are
consistent with the changeset; finally, update the PR description to summarize
what this patch (0.0.27) contains.

🪄 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: db9d08c5-225a-42d3-8f8c-0f68346d457f

📥 Commits

Reviewing files that changed from the base of the PR and between 9787a7e and d798485.

📒 Files selected for processing (1)

• packages/intent/package.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check if changeset files exist for this release

# Check for changeset files in the .changeset directory
echo "Checking for changeset files..."
fd -t f . .changeset -x echo "Found: {}"

# Also check if CHANGELOG.md has been updated
echo -e "\nChecking for changelog updates..."
if [ -f "packages/intent/CHANGELOG.md" ]; then
  echo "CHANGELOG.md exists"
  rg -n "0\.0\.27" packages/intent/CHANGELOG.md || echo "Version 0.0.27 not found in CHANGELOG"
else
  echo "No CHANGELOG.md found"
fi

Repository: TanStack/intent

Length of output: 213

---

🏁 Script executed:

# List all files in .changeset directory to see if there are any changeset entries
echo "=== Files in .changeset directory ==="
find .changeset -type f | sort

# Check the last few entries in CHANGELOG.md
echo -e "\n=== Last 30 lines of packages/intent/CHANGELOG.md ==="
tail -30 packages/intent/CHANGELOG.md

# Check if package.json in root mentions changesets
echo -e "\n=== Checking root package.json for changeset configuration ==="
rg -A 5 -B 5 'changeset' package.json || echo "No 'changeset' found in root package.json"

Repository: TanStack/intent

Length of output: 3569

---

Add a changeset entry for this patch release.

The project uses the @changesets/cli tool for version management, but no changeset entry file exists in the .changeset directory for version 0.0.27. The version was bumped directly in package.json instead of following the changesets workflow. Create a changeset entry using changeset command (or manually create a file in .changeset/ directory), then run changeset version to regenerate package.json and update CHANGELOG.md properly.

Additionally, the empty PR description should be filled with information about what changes are included in this patch release.

🤖 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 package.json version was bumped
directly to "0.0.27" without a corresponding changeset; create a new changeset
file in the .changeset directory (or run the changeset CLI) that declares a
patch release for the intent package and includes a short summary of the
changes, then run changeset version to regenerate package.json and update
CHANGELOG.md so the version and changelog are consistent with the changeset;
finally, update the PR description to summarize what this patch (0.0.27)
contains.