fix: resolve failed CI runs (release-please manifest + docs deploy CLI)

[jeffgreendesign]

Summary

Resolves the failed workflow runs from the last main commit/PR cycle (merge of #119). Two independent workflows were red; this PR fixes the in-code causes of both. Two remaining causes are repo settings and are noted at the bottom.

Changes

• Release Please — .release-please-manifest.json tracked 0.2.0 while package.json and the top CHANGELOG.md entry are both 0.4.0 (no git tags exist). release-please therefore computed a bogus next version (0.4.0 → 0.2.1). Bumped the manifest to 0.4.0 so releases are based on the real current version.
• Deploy Documentation Site — the deploy step failed with Your Vercel CLI version is outdated. This endpoint requires version 47.2.2 or later. because amondnet/vercel-action@v25 pins Vercel CLI 25.1.0. Added vercel-version: latest so a current CLI is installed.

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactoring
• Other (describe):

Checklist

• I've run pnpm typecheck with no errors (full pnpm verify:fast passed on the manifest change: 444 tests, lint, security, tool-sync)
• I've tested my changes locally with pnpm dev (n/a — CI config only)
• I've followed the code style
• I've updated documentation if needed (n/a)

Related Issues

Closes #

---

Requires repo settings (cannot be fixed in code)

• Release Please still needs Settings → Actions → General → Workflow permissions → "Allow GitHub Actions to create and approve pull requests" enabled, otherwise it fails with GitHub Actions is not permitted to create or approve pull requests.
• Deploy required the VERCEL_TOKEN / VERCEL_ORG_ID / VERCEL_PROJECT_ID repository Actions secrets — now configured (auth confirmed working in the latest run; only the CLI-version error remained, which this PR fixes).

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard	Building	Preview, Comment	Jul 11, 2026 11:05pm
textrawl	Ready	Preview, Comment	Jul 11, 2026 11:05pm

[coderabbitai]

Walkthrough

Updated the release manifest root component version from 0.2.0 to 0.4.0. Updated the Vercel deployment workflow to use the latest Vercel CLI, run from the repository root, and document the path-resolution behavior.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main CI fixes for Release Please and the Vercel deploy workflow.
Description check	✅ Passed	The description matches the template structure and covers summary, changes, type, checklist, and related issues, though the issue reference is left blank.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/failed-runs-resolution-g19x0d

---

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

[coderabbitai]

🧹 Nitpick comments (2)

.github/workflows/deploy-website.yml (2)

50-50: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Pin vercel-version instead of using latest.

The fix is well-reasoned and documented, but vercel-version: latest is a floating target: feat: add vercel-version option by @michalak111in#183`` shows this input exists specifically so a fixed CLI version can be selected. Since the underlying motivation for this change was Vercel's API rejecting an old pinned CLI without warning, relying on latest reintroduces the same class of risk in the opposite direction — a future Vercel CLI release could silently break `vercel-args: '--prod'` behavior or introduce required new flags with no corresponding change in this repo.

Consider pinning to a known-good, currently supported CLI version and bumping it deliberately (e.g., via Renovate/Dependabot) rather than tracking latest.

♻️ Suggested pin

-          vercel-version: latest
+          vercel-version: 47.2.2

Also applies to: 55-57

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/deploy-website.yml at line 50, Update the Vercel
deployment steps using amondnet/vercel-action@v25 to set vercel-version to a
specific known-good supported CLI version instead of latest. Apply the same
fixed version consistently to all occurrences, including the additional
deployment step, and leave the existing vercel-args configuration unchanged.

---

50-50: 🩺 Stability & Availability | 🔵 Trivial | 🏗️ Heavy lift

Consider upgrading amondnet/vercel-action itself instead of overriding its pinned CLI.

Line 50 still uses amondnet/vercel-action@v25, which is several years old and ships with Pin Vercel CLI to 25.1.0 by @vitorbalin#171`` baked in — hence the need for the vercel-version: latest workaround. Current README examples and Marketplace docs for this action now reference `uses: amondnet/vercel-action@v42`, a much newer major that may already track a current CLI baseline and avoid the double-path/root-directory quirks being worked around here.

Worth verifying whether upgrading to a current major resolves the CLI-version issue more cleanly (and picks up any Node 20 runtime fixes), rather than layering a version override on an outdated action pin.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/deploy-website.yml at line 50, Upgrade the deployment step
using the amondnet/vercel-action reference from `@v25` to the current documented
major, `@v42`, then verify whether the existing vercel-version override and
related path workarounds remain necessary; remove them if the upgraded action
handles the CLI and root-directory behavior correctly.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.github/workflows/deploy-website.yml:
- Line 50: Update the Vercel deployment steps using amondnet/vercel-action@v25
to set vercel-version to a specific known-good supported CLI version instead of
latest. Apply the same fixed version consistently to all occurrences, including
the additional deployment step, and leave the existing vercel-args configuration
unchanged.
- Line 50: Upgrade the deployment step using the amondnet/vercel-action
reference from `@v25` to the current documented major, `@v42`, then verify whether
the existing vercel-version override and related path workarounds remain
necessary; remove them if the upgraded action handles the CLI and root-directory
behavior correctly.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 81169ac7-d2d7-4baf-9c68-67155c7ca635

📥 Commits

Reviewing files that changed from the base of the PR and between bb03633 and 4384028.

📒 Files selected for processing (1)

• .github/workflows/deploy-website.yml