Skip to content
Skills Library
DevOps & cloud · Automation

release

/release

Release a Magento 2 module — bump version, update CHANGELOG, tag, push, publish. Use when the user wants to cut a release for a module. Detects the next version from conventional commits or accepts an explicit version. Validates before tagging, generates release notes from commits since last tag, and optionally creates a GitHub release.

Licence
MIT
Last repository change
04.10.2026

Assessment and security

100/ 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.
Content35 / 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
6
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.10.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

Release a Magento 2 module — bump version, update CHANGELOG, tag, push, publish. Use when the user wants to cut a release for a module. Detects the next version from conventional commits or accepts an explicit version. Validates before tagging, generates release notes from commits since last tag, and optionally creates a GitHub release.

Original author description

Release a Magento 2 module — bump version, update CHANGELOG, tag, push, publish. Use when the user wants to cut a release for a module. Detects the next version from conventional commits or accepts an explicit version. Validates before tagging, generates release notes from commits since last tag, and optionally creates a GitHub release.

How it works

  1. Core Rules
  2. Workflow
  3. Inputs
  4. Outputs
  5. Reference Files
  6. Templates
  7. Acceptance Criteria
  8. Multi-Module Repo
  9. Related Skills
Original SKILL.md headings · 181 lines, 884 words
SKILL.md preview
---
name: release
version: 1.2.1
description:
    Release a Magento 2 module — bump version, update CHANGELOG, tag, push, publish.
    Use when the user wants to cut a release for a module. Detects the next version from
    conventional commits or accepts an explicit version. Validates before tagging,
    generates release notes from commits since last tag, and optionally creates a GitHub
    release.
---

# Magento 2 Release

Cut a release for a Magento 2 module that lives in this repo.

## Core Rules

- **Validate first.** No release happens if pre-flight validation fails (
  `deploy --validate-only --strict --env=local`). The release MUST use `--validate-only` — never a
  state-changing deploy invocation.
- **Semver from commits.** Detect the next version from conventional commits, then let
  the user override.
- **Module-prefixed tags.** Multi-module repos need disambiguating tags:
  `{Vendor}_{Module}-{Version}`.
- **CHANGELOG kept in sync.** Bump CHANGELOG.md per module with grouped entries.
- **Confirm before push.** Tag pushing and GitHub Release creation require explicit
  user approval.
- **Never push to main without authorization.** This skill respects the project's branch
  protection rules.

## Workflow

### Phase 0 — Context Resolution

Invoke `context`. Capture `gh` CLI availability.

### Phase 1 — Determine Version

- Read current `composer.json` version.
- Read commits since last git tag matching `{Vendor}_{Module}-*` (or fall back to
  the initial commit if no prior tag). **Path-filter to this module** so commits from
  sibling modules in the same repo are excluded:
  `git log {lastTag}..HEAD -- {module_path}`.
- Classify each commit per conventional commits:
    - `feat:` → minor bump
    - `fix:` → patch bump
    - `BREAKING CHANGE:` or `feat!:` → major bump
- Propose next version. User can override with `--version=X.Y.Z`.
    - **Downgrade guard:** if an explicit `--version` is passed, refuse it unless it is
      strictly greater than the latest existing tag for this module (use the version
      comparison in `references/semver-rules.md`). A forced *upward* jump is still allowed
      (with a warning); a downgrade or equal version is rejected.

### Phase 2 — Validate

Run `deploy --validate-only --strict --env=local` against the local environment.
This is preflight-only — the deploy MUST NOT execute any state-changing step. All required
checks must pass before the release proceeds.

### Phase 3 — Update Files

- Bump `composer.json` version.
- Update `CHANGELOG.md` with grouped entries per `references/changelog-format.md`.
- Commit with message `release({Module}): {Version}`.

### Phase 4 — Tag

```
git tag -a {Vendor}_{Module}-{Version} -m "Release {Vendor}_{Module} {Version}"
```

Module-prefixed to disambiguate multi-module repos.

### Phase 5 — Push (APPROVAL GATE)

Confirm with user before pushing:

```
git push origin {current_branch}
git push origin {tag}
```

The user types **`release`** to confirm. Anything else cancels.

### Phase 5.5 — Render Release Notes

Render `templates/release-notes.md` from the Phase 1 classified commits to
`{output_root}/releases/{Module}-{Version}.md` (under the project-root, never under
`{magento_root}`; `{output_root}` is the `--docs-root` value or `{ctx.docs_root}`). This
file is the `--notes-file` source for Phase 6 **and** the durable release-notes artefact
listed in Outputs, so render it even when Phase 6 is skipped — otherwise Phase 6's
`gh release create --notes-file …` points at a path nothing created.

### Phase 6 — GitHub Release (Optional)

If `gh` is available and the user authorizes:

```
gh release create {tag} \
    --title "{Vendor}_{Module} {Version}" \
    --notes-file {output_root}/releases/{Module}-{Version}.md
```

### Phase 7 — Publish (Optional)

There is no `composer publish` command. "Publishing" means making the pushed tag
resolvable by a Composer source:

- **Packagist / Private Packagist:** the GitHub→registry webhook (or registry sync) picks
  up the tag automatically — no extra command. Verify on the package page if needed.
- **Satis:** regenerate the static repo with `satis build`.
- **Plain VCS source:** nothing to do — the consumer resolves the tag directly from git.
- **Marketplace (EQP):** prepare the zip artefact; the user uploads it via the Marketplace
  developer portal manually.

See `references/publish-targets.md`. Mostly a no-op for project-internal modules.

## Inputs

```
/release [--version=X.Y.Z] [--no-publish] [--no-github-release] [--dry-run] [--docs-root=<path>] <Vendor>_<Module>
```

| Flag                  | Default       | Meaning                           |
|-----------------------|---------------|-----------------------------------|
| `--version`           | auto-detected | Override the proposed version     |
| `--no-publish`        | off           | Skip Phase 7                      |
| `--no-github-release` | off           | Skip Phase 6                      |
| `--dry-run`           | off           | Print everything; make no changes |
| `--docs-root`         | unset         | Output-root override; see "Output root" below |

## Outputs

```
composer.json (updated)
CHANGELOG.md (updated)
git tag {Vendor}_{Module}-{Version}
GitHub Release page (if Phase 6 ran)

{output_root}/releases/{Module}-{Version}.md       # Generated release notes
```

`{output_root}` defaults to `.docs` (`{ctx.docs_root}`); see the `--docs-root`/`DOCS_ROOT`
recipe in `context/references/artifact-layout.md`.

### Output root (`--docs-root`)

This skill accepts `--docs-root=<path>` (see
`context/references/artifact-layout.md`). When set, write the run report (and any
report artifacts) under `<path>/releases/`; otherwise default to
`{ctx.docs_root}/releases/`. `feature` passes this so a feature run's
reports collect under its folder.

## Reference Files

- `references/semver-rules.md` — conventional commit → version bump rules.
- `references/changelog-format.md` — commit → category mapping and entry-generation
  procedure; cites `context/references/changelog-format.md` for structure.
- `references/tag-format.md` — multi-module tag prefix rules.
- `references/publish-targets.md` — Packagist, private Composer registries (Private Packagist / Satis / VCS),
  Marketplace EQP.

## Templates

- `templates/release-notes.md` — release notes structure.

## Acceptance Criteria

- Version bump matches semver convention.
- CHANGELOG entries reflect actual commits since last tag.
- No release happens if Phase 2 validate fails.
- Tag is signed if `git config tag.gpgsign` is true (tag signing reads `tag.gpgsign`, not `commit.gpgsign`).
- Release notes paste cleanly into GitHub Release.

## Multi-Module Repo

If multiple modules live in the same repo:

- Tag prefix disambiguates (`Acme_OrderExport-1.4.0` vs `Acme_Inventory-2.0.1`)
- Each module's `composer.json` is independent
- `CHANGELOG.md` lives in each module folder
- The skill releases ONE module per invocation

## Related Skills

| Phase | Skill                                                  |
|-------|--------------------------------------------------------|
| 0     | `context`                                     |
| 2     | `deploy --validate-only --strict --env=local` |
| 6     | external: `gh` CLI                                     |
Files in this package (6)
  • SKILL.md 7 KB
  • references/changelog-format.md 2 KB
  • references/publish-targets.md 4 KB
  • references/semver-rules.md 3 KB
  • references/tag-format.md 3 KB
  • templates/release-notes.md 1 KB

Versions

RepositoryScoreLicence
This page · muon-m2/magento2-tools100MIT
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 5b1127af4fa8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

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

Similar skills

  • 100ship-release
    Use when the user asks to release, ship, publish, cut or tag a version of a project ("release v0.2.0", "ship a patch", "bump and publish"). Bumps every version manifest, updates CHANGELOG and README badges, commits, lands it directly or through a pull request (pre-PR check,…
  • 100version-release
    Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".
  • 100release-plugin
    Cut a release of this repository - decide the version bump from the changes since the last tag, update plugin.json, CHANGELOG.md and the canvas footer, then tag and publish a GitHub release. Use when skill or canvas changes are ready to reach users, when the user asks to…
  • 100nvidia-nemoclaw-maintainer-cut-release-tag
    Cut a new semver release — bump all version strings via bump-version.ts, open a release PR, and after merge tag main and push. Use when cutting a release, tagging a version, shipping a build, or preparing a deployment. Trigger keywords - cut tag, release tag, new tag, cut…
  • 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-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.

Feedback and reports

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