Release plugin package

Resolve the package and target version from the request; ask only for missing required inputs. This skill prepares a PR, not an npm publication. Use release-core for the coupled core/create-rsbuild release.

Release changes

Inspect the branch and worktree, preserving unrelated changes. Isolate work when needed, and use a task branch before committing. Follow the user's or environment's branch naming convention; otherwise release/plugin-<name>-v<version> is a useful name.

Confirm that packages/plugin-<name>/package.json names the intended package. If this release already has version edits, a changelog entry, or a PR, read references/resume-release.md before choosing the baseline or editing.

For a new release, use the user-specified changelog baseline, or record the current package version and its release commit or tag before bumping it. Resolve an ambiguous range before generating the changelog.

Update:

• The plugin's package version.
• Its CHANGELOG.md, following the changelog rules below.
• Matching @rsbuild/plugin-<name> ranges in packages/create-rsbuild/template-*/package.json to ^<version>. Preserve workspace:* dependencies in packages/create-rsbuild/package.json.

Review the task diff against these fields and files. Preserve pre-existing unrelated changes. Investigate unexpected edits caused by the release work before committing.