Skip to content
Skills Library
DevOps & cloud · Learning & explanation

release

/release

Understand or change how Konstruct is versioned and released (prepare_release.py, the release workflow, GitHub releases, the v0 action tag, the gated PyPI job). Use when asked about versions, a release did not happen or was the wrong size, or publishing.

Repository
konstruct ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Understand or change how Konstruct is versioned and released (prepare_release.py, the release workflow, GitHub releases, the v0 action tag, the gated PyPI job). Use when asked about versions, a release did not happen or was the wrong size, or publishing.

Original author description

Understand or change how Konstruct is versioned and released (prepare_release.py, the release workflow, GitHub releases, the v0 action tag, the gated PyPI job). Use when asked about versions, a release did not happen or was the wrong size, or publishing.

How it works

SKILL.md has no level-two headings · 35 lines, 456 words

SKILL.md preview
---
name: release
description: Understand or change how Konstruct is versioned and released (prepare_release.py, the release workflow, GitHub releases, the v0 action tag, the gated PyPI job). Use when asked about versions, a release did not happen or was the wrong size, or publishing.
---

# Releases

- main is protected: nothing pushes to it, and a release is a tag plus a GitHub release.
- Changes accumulate on a branch as separate commits and merge in batches, about once an hour, by
  rebase, so each commit stays on main and in the changelog. Give the batch's pull request a plain
  title (not `feat(...): ...`): CI's Release preparation check counts a Conventional title as a
  commit, as it would be after a squash merge. The batch's last commit prepares the
  release: rebase on main, then run `uv run python .kodex/scripts/prepare_release.py`. It fetches
  main and the tags, reads every releasable commit on the branch since the last tag, and sets the
  next version in `pyproject.toml`, `uv.lock` (konstruct's own line only) and
  `konstruct/__init__.py`, with its section at the top of `CHANGELOG.md`. Running it again replaces
  that section. `--dry-run` prints the version and section. For a squash-merged pull request,
  `--title` counts its title when it is not one of the commits.
- The Release preparation job in Build and Test runs `--check` on every pull request: it passes when
  the pull request prepares no release, or prepares exactly what main now calls for, and fails when
  main has moved on (run the script again).
- While the version is 0.x a release is a patch, unless a change has `!` after its type or a
  `BREAKING CHANGE:` footer, which gives the next minor. The changelog follows commitizen's layout
  (BREAKING CHANGE from the footers' text, then Feat, Fix, Refactor and Perf). The script refuses to
  prepare 1.0 and the workflow refuses to release it: the owner decides that.
- `.github/workflows/release.yml` runs after Build and Test passes on main. It finishes a release
  left half done (tag pushed, no GitHub release); otherwise it tags a tested commit whose version
  has no tag; otherwise, when main has releasable commits since the last tag (a Dependabot fix, or a
  pull request merged without preparing), it runs the script on a detached commit above main and
  tags that. Tags are pushed only after the build succeeds. Each release moves `v0` and publishes
  the changelog section, wheel and sdist. A release made from a detached commit reaches main's
  `CHANGELOG.md` with the next prepared pull request, which copies its section from the tag.
- A run by hand (workflow_dispatch) only finishes a half-done release or tags a prepared version; it
  never releases from main's head. A run with nothing to release re-points `v0` at the latest
  release if it lags.
- **PyPI** is a separate job, off until the `PUBLISH_TO_PYPI` repository variable is `true` and a
  `pypi` environment with trusted publishing exists. Never turn it on without Dom's go-ahead.
- Never delete or move a published release tag other than `v0`.

Versions

RepositoryScoreLicence
This page · kodexlabsio/konstruct86MIT
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

Database snapshot: 13.11.2026 · package version 19d4dfa1796a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pypi-release
    Release a new seckit version to PyPI from this repository. Use when the user asks to publish, release, ship or tag a new version of seckit, bump the version, or check or fix the PyPI publish workflow.
  • 100release-publish
    Publishes a skforecast release to PyPI through the GitHub release and the publish-pypi.yml workflow (Trusted Publishing), after a rehearsal on TestPyPI. Use when the release branch X.Y.x is ready to be released.
  • 100cutting-a-release
    Use when cutting or publishing a tycoon release: opening the next version branch, finalizing CHANGELOG.md and docs/releases/, merging the release branch to main, pushing the version tag, or troubleshooting the PyPI trusted-publishing workflow.
  • 87release-please
    Set up and configure Google's release-please for automated versioning, changelog generation, and publishing via GitHub Actions. Covers pipeline creation, Conventional Commits formatting, pre-release workflows, monorepo configuration, and troubleshooting release pipelines. Use…
  • 100pypi-release
    This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPI_API_TOKEN secret.
  • 100geode-distribution
    Publish and verify a released GEODE version across GitHub Release and PyPI/uv. Use for uv/uvx distribution, stable promotions, release repair runs, and public installation-channel audits.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.