release
/release
Cut a release of one language's SDK with release-please, tags and release notes. Use when the user asks to release, publish, bump the version or write release notes.
- Author
- bitpin-dev ↗
- Repository
- bitpin-sdk ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Cut a release of one language's SDK with release-please, tags and release notes. Use when the user asks to release, publish, bump the version or write release notes.
Original author description
Cut a release of one language's SDK with release-please, tags and release notes. Use when the user asks to release, publish, bump the version or write release notes.
How it works
SKILL.md has no level-two headings · 14 lines, 298 words
SKILL.md preview
--- name: release description: Cut a release of one language's SDK with release-please, tags and release notes. Use when the user asks to release, publish, bump the version or write release notes. --- # Release Each language is a release-please component with its own version, `CHANGELOG.md` and tag: `python-v0.1.0`, `ts-v0.1.0`, `go/v0.1.0` and `java-v0.1.0`. The first Python release (0.1.0) also comes from a release PR: the manifest starts at 0.0.0. Versions follow SemVer; before 1.0, a breaking change bumps the minor version. 1. **Green main.** CI on `main` is green, and `sync-with-core` has been run since the last release if any endpoint changed. 2. **Commits drive notes.** release-please reads Conventional Commits since the last tag: `feat` → minor, `fix` → patch, `feat!`/`BREAKING CHANGE:` → major (minor before 1.0). Fix misleading commit subjects by editing the release PR's changelog, not history. 3. **Release PR.** The `release-please` workflow keeps a PR open per component. Review its `CHANGELOG.md`: every user-visible change is there in plain words, breaking changes say how to migrate. 4. **Ask** the user before merging the release PR. Merging creates the tag and the GitHub Release. 5. **Publish.** The release workflow builds and uploads to PyPI through trusted publishing when the release is created. TypeScript is *staged* on npm instead: a maintainer approves it on npmjs.com (or `npm stage approve <id>`) with 2FA before it goes live. Go has nothing to upload; the `go/vX.Y.Z` tag is the release. Java is signed and uploaded to the Maven Central Portal but not published: a maintainer presses *Publish* on central.sonatype.com (Deployments), because a Maven Central release can never be removed. Check: the version appears on https://pypi.org/project/bitpin-sdk/ and `pip install bitpin-sdk==<version>` works in a clean environment. 6. **Announce.** Give the user the release URL and the notes, in English and Persian if they ask. Manual fallback (no release-please): bump `python/pyproject.toml` and `__version__`, add the `CHANGELOG.md` section, commit `chore(release): python 0.x.y`, then, with approval, `git tag -a python-v0.x.y -m "..."`, push the tag and `gh release create`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · bitpin-dev/bitpin-sdk | 86 | MIT |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Database snapshot: 13.11.2026 · package version 474329c11a30 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100releasing
Full release lifecycle — version bump, CHANGELOG, rich release notes, tag, publish. Use when user says "release", "tag and release", "publish version", "cut a release", "new version". - 100release-notes
Write release notes or a changelog entry from git history. Use when the user asks for release notes, a changelog, "what changed since the last release", or a summary of commits between two tags or branches. - 100release-workflow
Release a new version of Atom-lite to npm and GitHub. Use when asked to release, publish, ship, bump version, cut a release, or prepare a release note/changelog. Covers version bump, gate checks, diff-driven changelog and release notes, tagging, publishing, and verification. - 100create-release
Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo. - 100release-notes
This skill should be used when the user asks to "create release note", "generate release notes", "release notes", "release changelog", "update GitHub release", or wants to generate categorized release notes between tags. Gathers PR/commit data via gh CLI, categorizes changes,… - 100azsdk-common-sdk-release
Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline…