skills.rest
ant-design
ant-designOFFICIAL
Explore all skills by this author →
Website𝕏@AntDesignUIGitHub

antd-version-release

Prepare release PRs and publish npm versions for the ant-design repository.

99.3k|54.7k|Updated Apr 24, 2015
Search Tags:#release#npm publish#Versioning#Workflow#ant-design#Pull request#ChangeLog
One-click install
npx skills add https://github.com/ant-design/ant-design --skill antd-version-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antd-version-release
Source: https://github.com/ant-design/ant-design/tree/main/.agents/skills/version-release
Command: npx skills add https://github.com/ant-design/ant-design --skill antd-version-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a new version of ant-design requires coordinating branch selection, changelog alignment, version bumps, and npm publishing without breaking the repository's release workflow. This Skill enforces the exact conventions used by the ant-design maintainers.

Core Features & Use Cases

  • Release PR Preparation: Update package.json and changelog files, then open a properly titled PR against master or a stable maintenance branch.
  • Version Type Detection: Decide between patch and minor releases based on whether new features are included.
  • npm Publishing: Execute npm publish after the release PR is merged, relying on prepublishOnly and postpublish hooks for CI checks and tag creation.
  • Use Case: A maintainer wants to ship a bugfix release. They confirm the changelog is ready, bump the patch version in package.json, run npm run lint:changelog, open a docs: release x.y.z PR, and after merge run npm publish to push the package.

Quick Start

Use the antd-version-release skill to prepare a patch release PR for the current ant-design branch and publish it after merge.

Frequently Asked Questions about antd-version-release

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

FAQPage Schema
How do I prepare a release PR for ant-design?▼

Confirm the changelog files contain the target version section, update `package.json` to the new version, run `npm run lint:changelog`, then open a PR titled `docs: release x.y.z` against `master` using the official PR template.

What command publishes the antd npm package?▼

Run `npm publish` after the release PR is merged and the working tree is clean. Do not use `npm run pub`, and avoid manually creating Git tags since `postpublish` handles tag pushing.

How do I decide between a patch and minor release?▼

If the changes include unreleased new features from a `feature` branch, treat the release as minor and bump the middle version. Otherwise default to patch and increment the patch number.

Why does the release PR title need a version number?▼

The `.github/workflows/verify-package-version.yml` workflow validates that any PR title containing `release` or `changelog` includes the target version number, ensuring traceability of release commits.

Can I publish without a changelog entry?▼

No. `scripts/check-version-md.ts` requires a matching changelog section in both `CHANGELOG.en-US.md` and `CHANGELOG.zh-CN.md` with a date close to the publish date before allowing the release.

Related Skills

Explore More Software Engineering Skills→
KauedzKauedz

release-changelog

Generate a stable Paperclip release changelog from git logs, changesets, and merged PRs.

Community
Advanced
bmad-code-orgbmad-code-org
51.7k

bmad-os-release-module

Automates npm release process including changelog drafting, versioning, git tagging, publishing, and GitHub releases.

Official
Advanced
theslashdojotheslashdojo

npm-publish

Automate npm package publishing with pre-flight checks and provenance.

Official
Advanced
phrazzldphrazzld

changelog-automation

Automate changelog generation and semantic versioning with Changesets or semantic-release.

Community
Advanced