PrestaShopCorp/ps_mbo / .claude/skills/release-versioning
release-versioning
VerifiedVersion bump + GitHub release workflow for ps_mbo. Analyzes commits since last tag, proposes patch/minor bump, checks hooks for upgrade file need, commits the bump, creates the GitHub release with auto-generated changelog, then produces a short non-technical changelog for the Addons Marketplace.
Release Versioning Workflow
Use this skill to bump the module version and publish a GitHub release.
Step 1: Ensure clean state on master
git checkout master
git fetch origin
git pull origin master
If there are uncommitted changes, stop and ask the user to commit or stash them first.
Step 2: Identify current state
git describe --tags --abbrev=0 # e.g. v5.2.2
git log <last_tag>..HEAD --oneline --no-merges
Also read:
ps_mbo.php:const VERSION = '...'and$this->version = '...'config.xml:<version><![CDATA[...]]></version>
Note the last-tag version (e.g., 5.2.2) and the current file version (may already be bumped).
Step 3: Analyze commits and propose bump
Scan commit messages since the last tag:
| Commit type | Bump type |
|---|---|
feat: or feat(...): | minor (x.Y.0) |
BREAKING CHANGE in body | Refuse major, apply minor and flag it |
fix:, chore:, refactor:, docs:, ci:, perf:, test: | patch (x.y.Z) |
| No conventional prefix | patch (assume patch, flag as ambiguous) |
Highest-priority rule wins: any feat: -> propose minor, else -> propose patch.
Present both options to the user, pre-selecting the recommended one. Never propose major.
Step 4: Check hooks for upgrade file
Detect hook-related changes since the last tag:
git diff --name-status <last_tag>..HEAD -- src/Traits/Hooks/
git diff <last_tag>..HEAD -- ps_mbo.php | grep -E "^\+.*hook|^\-.*hook"
If any hook trait was added or removed, or the hooks list in ps_mbo.php changed:
- Check if
upgrade/upgrade-<new_version>.phpalready exists. - If it does not exist, propose creating it with this template:
<?php
/**
* Copyright since 2007 PrestaShop SA and Contributors
* PrestaShop is an International Registered Trademark & Property of PrestaShop SA
*
* NOTICE OF LICENSE
*
* This source file is subject to the Academic Free License version 3.0
* that is bundled with this package in the file LICENSE.md.
* It is also available through the world-wide-web at this URL:
* https://opensource.org/licenses/AFL-3.0
* If you did not receive a copy of the license and are unable to
* obtain it through the world-wide-web, please send an email
* to license@prestashop.com so we can send you a copy immediately.
*
* @author PrestaShop SA and Contributors <contact@prestashop.com>
* @copyright Since 2007 PrestaShop SA and Contributors
* @license https://opensource.org/licenses/AFL-3.0 Academic Free License version 3.0
*/
if (!defined('_PS_VERSION_')) {
exit;
}
$rootDir = defined('_PS_ROOT_DIR_') ? _PS_ROOT_DIR_ : getenv('_PS_ROOT_DIR_');
if (!$rootDir) {
$rootDir = __DIR__ . '/../../../';
}
require_once $rootDir . '/vendor/autoload.php';
/**
* @param ps_mbo $module
*
* @return bool
*/
function upgrade_module_<version_underscored>(Module $module): bool
{
$module->updateHooks();
return true;
}
Replace <version_underscored> with the new version using underscores (e.g., 5_2_3 for version 5.2.3).
If no hook changes are detected, skip this step silently.
Step 5: Confirm and apply the bump
Once the user confirms the target version:
If files already have this version (detected in Step 2):
- Say: "Files already at vX.Y.Z (bumped in commit abc1234). No new bump commit needed."
- Jump to Step 6.
If files are still on the old version:
- Update
ps_mbo.php:const VERSION = '<new_version>';$this->version = '<new_version>';
- Update
config.xml:<version><![CDATA[<new_version>]]></version>
- Stage and commit (include upgrade file if created in Step 4):
git add ps_mbo.php config.xml git commit -m "chore: bump version <old_version> -> <new_version>" git push origin master
If an upgrade file was created but the version bump was already committed separately:
git add upgrade/upgrade-<new_version>.php
git commit -m "chore: add upgrade script for v<new_version>"
git push origin master
Step 6: Create the GitHub release
gh release create v<new_version> \
--title "v<new_version>" \
--generate-notes \
--target master
Output the release URL.
Step 7: Produce the Marketplace changelog
The GitHub auto-notes are too technical for the Addons Marketplace. Generate a short, merchant-facing changelog from the same commits analyzed in Step 2.
Rules for the Marketplace changelog:
- English, plain language, no internal/technical terms (no class names, no PHP version internals unless merchant-relevant, no refactor/CI/chore noise).
- Group commits by merchant-visible benefit, not by commit type.
- 2 to 4 bullet points max. Collapse internal-only work (refactor, ci, chore, build, test, deps) into a single line like "Stability, performance, and security improvements."
- Keep
feat:/fix:user-facing changes as their own bullets, reworded as benefits.
Output it in a fenced block titled What's new in <new_version> so it can be pasted
directly into the Marketplace. Example shape:
What's new in <new_version>
- <feature reworded as a merchant benefit>
- <user-facing fix reworded>
- Stability, performance, and security improvements.
Rules
- Never bump major. If breaking changes detected, apply minor and note it.
- Tag format:
v<major>.<minor>.<patch>(e.g.,v5.2.3). Release name = tag name. --generate-notesuses GitHub's auto-changelog from commits between the previous and new tag.- If branch protection prevents direct push to master: use
chore/bump-<new_version>branch, open PR, merge, then rungh release createafter merge.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |