원클릭으로
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.