fix: trigger new releases with Trusted Publishing

[serhalp]

Make some silly changes in each package to trigger a patch bump in each.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2278d611-bd2f-4ae7-9325-81af15c1868d

📥 Commits

Reviewing files that changed from the base of the PR and between ff9a358 and 833e8d3.

📒 Files selected for processing (3)

• packages/nuxt-module/README.md
• packages/vite-plugin-tanstack-start/README.md
• packages/vite-plugin/README.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• netlify/blueprints (manual)

💤 Files with no reviewable changes (1)

• packages/nuxt-module/README.md

✅ Files skipped from review due to trivial changes (2)

• packages/vite-plugin-tanstack-start/README.md
• packages/vite-plugin/README.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated the Vite plugin “Feature Support” table to include AI Gateway and Database.
  • Adjusted the Vite plugin installation command to use the development dependency flag.
  • Refreshed README badge reference details and updated a configuration options link domain.

Walkthrough

Three README files across different packages are updated with minor documentation changes. In packages/vite-plugin/README.md, the feature support table gains two new rows marking AI Gateway and Database as supported, and the npm installation command is updated to include the -D dev-dependency flag. In packages/nuxt-module/README.md, the npm downloads badge reference definitions are removed from the Badges section. In packages/vite-plugin-tanstack-start/README.md, the documentation link in the configuration options code block comment is updated from npmjs.com to npmx.dev.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix: trigger new releases with Trusted Publishing' is vague and doesn't describe the actual changes (README badge/documentation updates) made in the changeset.	Consider a more descriptive title that reflects the actual changes, such as 'chore: update package README files' or 'docs: update README documentation across packages'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description adequately explains the intent (trigger patch bumps) and is related to the changeset's purpose of making deliberate changes to increment versions.
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 serhalp/force-releases

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 08e605d267

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".