jerryshao opened a new pull request, #10479:
URL: https://github.com/apache/gravitino/pull/10479
### What changes were proposed in this pull request?
- Adds `dev/release/gravitino-release/SKILL.md`: a Claude Code skill that
acts as an interactive release manager, guiding through all 7 stages (tag,
build, docs, publish, docker, finalize, release-note) with state tracking, mock
mode, dry-run support, preflight checks, and credential collection.
- Adds `dev/release/mock/do-release.sh` and
`dev/release/mock/publish-docker.sh`: mock scripts that simulate all stages
without real operations, for safe end-to-end testing of the skill.
- Fixes `STATE_DIR` path bug in `do-release.sh`, `mock/do-release.sh`, and
`publish-docker.sh`: the default `.release-state` was a relative path, causing
state files to be written to the caller's working directory instead of
alongside the scripts. Fixed to use `$SELF/.release-state`.
- Fixes log file path bug in `mock/do-release.sh`: log files also used a
relative path; fixed to use `$SELF/${STEP}.log`.
### Why are the changes needed?
Fix: #10478
The release process is complex and multi-staged. Without structured tooling,
a release manager must remember which stages have run, which credentials are
needed, and how to recover from failures. The skill automates this
orchestration. The state-dir bug caused state files to be scattered in
unpredictable locations depending on where scripts were invoked from, breaking
resume-after-failure behavior.
### Does this PR introduce _any_ user-facing change?
No API or property key changes. The skill and mock scripts are new developer
tooling only.
### How was this patch tested?
Tested end-to-end using mock mode (`dev/release/mock/do-release.sh`) with
all 7 stages, including failure simulation via `MOCK_FAIL_STAGE`, dry-run mode,
and resume-from-partial-state scenarios.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
