fix(release): bump ClawHub skill resource versions to 0.8.9 - #177
Merged
Conversation
The rafter-security-skill.md frontmatter version (Node + Python copies) was left at 0.8.7 through the 0.8.8 and 0.8.9 package bumps, failing the validate-release 'ClawHub skill version matches package version' gate on the main→prod PR (#176). More importantly, publish-clawhub uses this frontmatter version as the ClawHub release version — so deploying as-is would ship the skill at a stale 0.8.7 while npm/PyPI publish 0.8.9 (cross-registry skew). Bump both to match the package version. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
2 participants
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.
Fixes the two failing
validate-versionschecks on the main→prod release PR (#176).Root cause
node/resources/rafter-security-skill.mdandpython/rafter_cli/resources/rafter-security-skill.mdcarry aversion:frontmatter field thatvalidate-release.ymlrequires to match the package version. They were left at 0.8.7 through the 0.8.8 (#170) and 0.8.9 (#175) bumps — the release PRs bumpedpackage.json/pyproject.tomlbut missed these.validate-versionsonly runs as a gate on PRs→prod (and on push→main, post-merge, non-blocking), which is why it didn't surface until #176.Why it matters (would it block the deploy?)
The deploy workflow
publish.yaml(push→prod) doesn't re-runvalidate-versions, so it wouldn't be aborted by the red checks. Butpublish-clawhubuses this SKILL.md frontmatter version as the ClawHub release version — so deploying as-is would publish npm/PyPI at 0.8.9 while ClawHub ships the skill at a stale 0.8.7 (cross-registry skew), and the published packages would internally claim 0.8.7. That's exactly the drift the gate guards against.Fix
Bump both resource files
0.8.7 → 0.8.9(verified thevalidate-versionslogic passes locally). Once this merges tomain, #176 picks it up and goes green.🤖 Generated with Claude Code