fix(ci): preserve release PR title in publish-release job

[paulbalaji]

Summary

• Added title: 'chore: release npm packages' to publish-release job's changesets action

Problem

The release PR title was reverting from "chore: release npm packages" back to "Version Packages" (see #7785).

Root cause: Both prepare-release and publish-release jobs run changesets/action with version: pnpm version:prepare. The version:prepare script includes turbo run version:update which regenerates typescript/cli/src/version.ts unconditionally.

When publish-release runs:

1. Checks out main (with old version in version.ts)
2. Runs version:prepare which regenerates version.ts
3. Changesets action detects dirty file and commits "Version Packages"
4. Updates PR without title parameter → reverts to default "Version Packages"

Fix

Add title parameter to publish-release job so it preserves the correct PR title.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Improved release workflow configuration to generate clearer and more consistent changelog entries during package releases.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 13a75d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

This change adds title parameters to the changesets/action@v1 steps in both the prepare-release and publish-release jobs within the GitHub Actions release workflow, setting the title to 'chore: release npm packages' for consistent changelog entries.

Changes

Cohort / File(s)	Summary
Release workflow configuration .github/workflows/release.yml	Added title: 'chore: release npm packages' parameter to both the prepare-release and publish-release job changesets/action steps (2 additions)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix(ci): remove duplicate title key in release workflow #7510: Modifies the same changesets action title input in the release workflow
• feat: update PR title to pass PR title lint ci #7358: Updates GitHub workflow release PR titles to use the "chore:" prefix convention

Suggested reviewers

• antigremlin
• yjamin

Poem

Like an onion's layers, all things have their place,
A title for the changelog, simple and clean,
"Chore: release" whispers through the workflow's space,
Two steps aligned—no fuss, no mess, no brace,
Just what's needed, nothin' fancy in between. 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description covers the problem, root cause, and fix clearly. However, it doesn't follow the repository's template structure with required sections like Related issues, Backward compatibility, and Testing.	Consider restructuring the description to match the template: add Related issues section (#7785), confirm backward compatibility, and specify testing type (Manual/Unit Tests).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main fix: preserving the release PR title in the publish-release job by adding the title parameter.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/release-pr-title

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.02%. Comparing base (2c0b865) to head (13a75d3).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7850   +/-   ##
=======================================
  Coverage   77.02%   77.02%           
=======================================
  Files         117      117           
  Lines        2651     2651           
  Branches      244      244           
=======================================
  Hits         2042     2042           
  Misses        593      593           
  Partials       16       16           

Components	Coverage Δ
core	87.80% <ø> (ø)
hooks	71.86% <ø> (ø)
isms	81.10% <ø> (ø)
token	86.67% <ø> (ø)
middlewares	84.98% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.