docs(release): check the downstream hwpx skill for CLI drift - #48
Merged
Conversation
The hwpx skill in STAIxBWLB/skills shells out to this binary, so a release that changes the CLI surface can invalidate it. v0.7.0 did exactly that: the skill still records docx as unsupported and omits it from its hardcoded --to choices (STAIxBWLB/skills#6). That repo now runs a daily drift check, so this is a belt-and-braces item -- a release that changes the CLI surface should not wait on someone else's cron. Both language sides updated together per the documentation policy.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the release readiness checklist to explicitly include a manual check for downstream CLI-surface drift in the STAIxBWLB/skills repo’s skills/hwpx skill, ensuring releases that change the hwp CLI don’t leave the downstream skill broken until its daily drift detector reports it.
Changes:
- Add a new checklist item to review
STAIxBWLB/skillsskills/hwpxfor CLI-surface drift before releasing. - Apply the same checklist update to both the English and Korean release readiness documents (bilingual policy preserved).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/release-readiness.md | Adds a release checklist item to manually verify downstream skills/hwpx remains compatible with CLI changes. |
| docs/release-readiness.ko.md | Korean counterpart of the same new downstream drift check item. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One checklist line in
docs/release-readiness.mdand its Korean counterpart.Why
The
hwpxskill in STAIxBWLB/skills shells out to thehwpbinary, so a release that changes the CLI surface can invalidate it without anything in this repo looking wrong. v0.7.0 did exactly that: the skill still records docx as✗ 미지원and omits it from its hardcoded--tochoices, making the new format unreachable through the skill. Filed as STAIxBWLB/skills#6.That repo now has a daily drift detector (STAIxBWLB/skills#7) that opens an issue when its recorded
verified_releasefalls behind our latest tag. This checklist line is the belt-and-braces half: a release that changes the CLI surface should not wait up to a day for someone else's cron to notice.Both language sides are updated in the same commit per the documentation policy in
CLAUDE.md.No code changes; CI is the usual fmt/clippy/test gates.