rspack-release-pr

Creates official Rspack release pull requests with version bumps and Ecosystem CI triggers.

12.9k|843|Updated Apr 1, 2022
One-click install
npx skills add https://github.com/web-infra-dev/rspack --skill rspack-release-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rspack-release-pr
Source: https://github.com/web-infra-dev/rspack/tree/main/.agents/skills/rspack-release-pr
Command: npx skills add https://github.com/web-infra-dev/rspack --skill rspack-release-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing an official Rspack release involves many error-prone manual steps: cleaning the worktree, syncing to origin/main, bumping JavaScript and Rust versions, opening a PR, and triggering Ecosystem CI. This Skill automates that entire workflow with built-in safety gates and confirmation checkpoints.

Core Features & Use Cases

  • Automated version bumping: Runs ./x version for major, minor, or patch releases, with optional --pre alpha|beta|rc pre-release tags, updating both JavaScript packages and the Rust workspace.
  • Safety gates: Stops on staged changes, requires explicit authorization before discarding unstaged work, and pauses for user confirmation of the new JS and Rust versions before committing.
  • PR creation and CI trigger: Pushes the release branch, opens a PR with standardized release metadata, and dispatches the Ecosystem CI workflow, then reports the PR and workflow run URLs.
  • Use Case: A maintainer needs to cut a patch release of Rspack. The Skill cleans the checkout, syncs to the latest main, bumps versions, confirms them, opens the release PR, and triggers Ecosystem CI in one guided flow.

Quick Start

Use the rspack-release-pr skill to prepare an official patch release pull request for Rspack.

Frequently Asked Questions about rspack-release-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an official Rspack release pull request?

Run the release workflow from a clean checkout synced to origin/main, then execute ./x version with major, minor, or patch. After confirming the new JavaScript and Rust versions, the workflow commits, pushes a chore/release-YYYY-MM-DD branch, and opens the PR with gh.

How do I publish an alpha, beta, or rc pre-release of Rspack?

Pass the --pre flag to the version command, for example ./x version patch --pre rc or ./x version minor --pre beta. Only alpha, beta, and rc pre-release tags are allowed; snapshot, debug, and canary flows are not supported by this workflow.

Where are the Rspack JavaScript and Rust versions defined?

The JavaScript package version is read from packages/rspack/package.json, and the Rust crate version comes from [workspace.package].version in the root Cargo.toml. Both are shown for user confirmation before any commit or push happens.

What happens if my git working tree has uncommitted changes?

The workflow stops if staged changes exist and asks how to handle them. Unstaged or untracked changes are only discarded with git restore and git clean after you explicitly authorize it, since the release PR must start from a fully clean tree.

Does the release workflow trigger Ecosystem CI automatically?

Yes, after the PR is created it dispatches the ecosystem-ci.yml workflow with the PR number via gh workflow run. It then polls until a new workflow_dispatch run appears and reports both the PR URL and the Ecosystem CI run URL.