بنقرة واحدة
release-orchestration
Activate this skill whenever preparing a release, bumping versions, or creating tags.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Activate this skill whenever preparing a release, bumping versions, or creating tags.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Activate this skill whenever writing tests, running linters, or committing code.
Activate this skill whenever opening Pull Requests, creating branches, or responding to GitHub issues.
Activate this skill whenever designing new features, modifying Docker compose logic, or interacting with Liferay environments.
Run FIRST before any task when workspace root lacks AGENTS.md. Creates AGENTS.md tailored to the Python environment (pyproject.toml, .venv, pytest).
Guides agents on documenting, naming, and categorizing upstream bugs/limitations in the repository's JIRA issue tracker.
Guides and scripts for developing, testing, linting, and releasing Liferay Docker Manager (LDM).
| name | release-orchestration |
| description | Activate this skill whenever preparing a release, bumping versions, or creating tags. |
pyproject.toml, constants.py), or create/push git tags. You MUST always use the automated orchestrator script:
To bump versions and tag pre-releases:
python3 scripts/release.py --bump beta
To promote pre-releases to stable releases (must be run from the active release branch):
python3 scripts/release.py --promote
To prevent "version fatigue" and ensure the stability of the main release channel:
v2.10.x-pre.y) first.v2.15.19) is pushed, it is permanently locked to that commit. Any premature tagging permanently burns the version number, requiring a version bump to recover. You MUST be absolutely certain all pre-requisites are met before tagging.[release]) MUST be reserved for hardened features and verified bugfixes.