release
/release
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing patch releases.
- Author
- automattic ↗
- Repository
- wordpress-activitypub ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.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
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing patch releases.
Original author description
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing patch releases.
How it works
- Quick Reference
- Comprehensive Release Guide
- Release Workflow
- Changelog Management
- Version Numbering
SKILL.md preview
--- name: release description: Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing patch releases. --- # ActivityPub Release Process Quick reference for managing releases and changelogs for the WordPress ActivityPub plugin. ## Quick Reference ### Release Commands ```bash npm run release # Create major/minor release PR. ``` ### Version File Locations When updating versions manually, change these files (these are the files `bin/release.js` touches): - `activitypub.php` - Plugin header (`Version: X.Y.Z`) **and** the `ACTIVITYPUB_PLUGIN_VERSION` constant. Both must change. - `readme.txt` - WordPress.org readme (`Stable tag: X.Y.Z`). - `includes/class-migration.php` - Version references in the DB-migration `version_compare()` checks. - `CHANGELOG.md` - Changelog file (auto-updated by release script). Note: `package.json` has no `version` field and is not part of the release bump. ## Comprehensive Release Guide See [Release Process](docs/release-process.md) for complete release workflow and detailed steps. ## Release Workflow ### Major/Minor Releases **Quick workflow:** ```bash # 1. Run release script from plugin root. npm run release # Script automatically: # - Determines version from changelog entries. # - Updates version numbers in all files. # - Updates CHANGELOG.md. # - Creates PR for review. # 2. Review and merge the release PR. # 3. Create GitHub release from trunk using the new tag. ``` See [Release Process - Major/Minor](docs/release-process.md) for detailed steps. ### Patch Releases **Quick workflow:** ```bash # 1. Create branch from the tag to patch. git fetch --tags git checkout -b tags/5.3.1 5.3.0 # Patch 5.3.0 -> 5.3.1 # 2. Cherry-pick merge commits from trunk (note -m 1 flag). git cherry-pick -m 1 <commit-hash> # 3. Update changelog and versions. composer changelog:write # Manually update versions in (see Version File Locations above): # - activitypub.php (Version header AND ACTIVITYPUB_PLUGIN_VERSION constant) # - readme.txt # - includes/class-migration.php # 4. Push branch and create GitHub release. git push -u origin tags/5.3.1 ``` **Important:** Use `-m 1` flag when cherry-picking merge commits to select the mainline parent. See [Release Process - Patch Releases](docs/release-process.md#patch-releases) for detailed steps. ## Changelog Management ### How It Works Changelogs are managed automatically through the PR workflow: 1. **PR Template** (`.github/PULL_REQUEST_TEMPLATE.md`): - Check "Automatically create a changelog entry" checkbox. - Select significance: Patch/Minor/Major. - Select type: Added/Fixed/Changed/Deprecated/Removed/Security. - Write message **ending with punctuation!** 2. **GitHub Action** (`.github/workflows/changelog.yml`): - Creates changelog file from PR description. - Validates proper punctuation. - Saves to `.github/changelog/` directory. 3. **Release Process**: - `npm run release` aggregates all entries. - Updates `CHANGELOG.md` and `readme.txt` automatically. ### Critical Requirements **Always end changelog messages with punctuation:** ``` ✅ Add support for custom post types. ✅ Fix signature verification bug. ❌ Add support for custom post types ❌ Fix signature verification bug ``` **Write end-user friendly messages:** - Focus on user benefit, not implementation details. - Avoid technical jargon where possible. - Describe what users can now do, not how it works internally. ``` ✅ Add pre-built block patterns for easy profile and sidebar setup. ✅ Fix follow button not appearing on author pages. ❌ Add register_patterns() method to class-blocks.php. ❌ Refactor User class to use Actors collection. ``` **Pick the significance by what breaks for a real install:** - `major` bumps the plugin to the next whole version, so it has to be worth that: a user who keeps doing what they did before gets a materially worse or destructive result on a surface real installs depend on. Removing a public constant or breaking an opt-in experiment is not `major`. Raising the minimum WordPress or PHP version always is. - Check that the break actually broke something before claiming it. **One entry per user-visible change.** Split unrelated fixes into separate files, but several fixes to the same visible thing are one entry, however many issues they close. **No entry for a bug that never shipped.** A fix for something introduced on the same unreleased branch is net zero for users. **Release PR bodies stay neutral.** Use the release script's plain text; never enumerate or spotlight security fixes in a release PR or its notes. **Never mention AI tools or coding assistants in changelog messages.** See [PR Workflow - Changelog](../pr/SKILL.md#changelog-management) for complete changelog requirements. ## Version Numbering **Semantic versioning:** - **Major (X.0.0)** - Breaking changes. - **Minor (0.X.0)** - New features, backward compatible. - **Patch (0.0.X)** - Bug fixes only. The release script determines version automatically from changelog entry significance levels.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · automattic/wordpress-activitypub | 100 | 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 43eab2cf68b8 (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
- 100release-management
Manage releases with release-please, version bumps, and changelog generation. Use when preparing releases, debugging release failures, or understanding version history. - 100sentry-release-management
Manage Sentry releases and associate commits. Use when creating releases, tracking commits, or managing release artifacts. Trigger with phrases like "sentry release", "sentry commits", "manage sentry versions", "sentry release workflow". - 100release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog,… - 90release-manager
Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates. - 100releasing-plugin-versions
Use when releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases for this marketplace - 100flux-controller-patch-releases
Run the upstream Flux controller patch release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when preparing a new controller patch release from a…