fix(ci): skip stale workflow results and quote headers

[harlan-zw]

🔗 Linked issue

Follow-up to #956.

📚 Description

The release workflow can receive CI results from commits made before release automation existed. Those checkouts lack the planning script, so release preparation fails.

Skip those historical CI results. Use consistent quoting for registry request headers to satisfy the lint rule.

The package size report can also finish after its PR closes or moves to another commit. Skip comments for those stale results.

🤖 AI disclosure: Harlan Agent Kit modified this description. My AI open-source policy.

[vercel]

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

Project	Deployment	Actions	Updated
scripts-playground	Ready	Preview	Oct 12, 2026 12:46pm UTC

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 11b8699b-b85f-48cc-af23-acc49f46802c

---

📥 Commits

Reviewing files that changed from the base of the PR and between 34e68ac and a1a7e89.

---

📒 Files selected for processing (2)

• .github/workflows/release.yml
• scripts/check-release-channel.ts

---

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.

---

---

📝 Walkthrough

📝 Walkthrough

Walkthrough

The release-planning step skips the planner for workflow_run events when the checked-out commit lacks scripts/prepare-release.ts, and sets the release output to false. Other events continue to run the planner. The registry request now quotes the accept header key; its value and other request options are unchanged.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

---

Merge Risk: ⚪ Minimal · up to a1a7e

The historical-run guard skips planning when the checked-out commit lacks the planner, without triggering release actions. The header edit does not change registry requests; no actionable merge risk remains.

Pre-merge checks | 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly summarizes both main changes: skipping stale release workflow results and quoting registry headers.
Description check		The description directly explains the stale workflow result problem and the registry header quoting change.

---

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

---

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/scripts-devtools@960

npm i https://pkg.pr.new/@nuxt/scripts@960

commit: a1a7e89