git-release
Semantic versioning and release workflow for creating and publishing package releases.
- License 许可
- MPL-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- git-release
- updated
- 1778976000000
- description
- Semantic versioning and release workflow for creating and publishing package releases.
- when_to_use
- Use this skill when preparing a new software release and you need a consistent semantic versioning and changelog workflow.
03 SKILL.md 正文
Git Release
This skill documents a small, repeatable release workflow using semantic versioning (SemVer) and a changelog. It focuses on the schema and structure of the release process so teams can follow a consistent pattern.
When To Use
Use this when you are about to publish a new release (library, CLI, service) and need to:
- Choose the next SemVer number.
- Update the changelog with a short summary of notable changes under the new version heading.
- Update the project's version metadata (
package.json,pyproject.toml,go.mod, etc.) if applicable. - Tag the release in git and push artifacts/tags.
Versioning (SemVer)
- MAJOR: Incompatible API changes or breaking changes.
- MINOR: Backwards-compatible new features or enhancements.
- PATCH: Backwards-compatible bug fixes and small tweaks.
Tag format recommendation: vMAJOR.MINOR.PATCH (for example v1.2.3).
Release Process (Structured Steps)
- Determine the next version (MAJOR.MINOR.PATCH) based on merged changes and SemVer rules.
- Update the changelog with a short summary of notable changes under the new version heading.
- Update the project's version metadata (
package.json,pyproject.toml,go.mod, etc.) if applicable. - Commit the version and changelog changes to the release branch.
- Create a signed or annotated git tag using the chosen tag format.
- Push commits and tags to the remote repository.
- Publish artifacts (package registry, container registry, GitHub Release) according to your release pipeline.
Minimal Command Examples
-
Commit and tag (example):
git add CHANGELOG.md package.json && git commit -m "chore(release): v1.2.0"git tag -a v1.2.0 -m "Release v1.2.0"git push origin main --follow-tags
-
Using npm for version bump (example):
npm version patch -m "chore(release): %s"(creates commit + tag)git push origin --follow-tags
Adjust these commands to match your language/tooling conventions.
Changelog Guidance
- Put a short, human-readable entry for each noteworthy change under the new version heading.
- Use categories if helpful (e.g., Added, Changed, Fixed, Security).
- Prefer linkable references to PR numbers or issue IDs for traceability.
Notes & Conventions
- Keep tag names consistent (recommended: leading
v). - Prefer annotated tags when you want release messages and signing:
git tag -a vX.Y.Z -m "Release vX.Y.Z". - Ensure CI/CD or release automation uses the same version source (tag or file) to avoid drift.
Minimal Checklist
- [ ] Version chosen and validated
- [ ] CHANGELOG updated
- [ ] Version metadata updated (if needed)
- [ ] Commit created with release changes
- [ ] Tag created (annotated or signed)
- [ ] Commits and tags pushed
- [ ] Artifacts published
04 同仓库更多 Skills
tax-filing-checklist
Walk through the steps and documents needed to file an individual federal income tax return
patient-vitals-charting
Record patient vital signs consistently and flag values outside the normal reference range
pasta-from-scratch
Make fresh egg pasta dough from scratch, roll it, and cut it into shapes
knife-sharpening
Sharpen and hone kitchen knives to keep an edge safe and effective
first-aid-response
Respond to a first aid emergency using a scene-safety-first, ABC-based (airway, breathing, circulation) approach
contract-review-basics
Review a contract draft for missing terms, ambiguous language, and risky clauses before signing