fix(ci): use 'rafter' as the ClawHub owner handle#96
Merged
Conversation
The actual handle on clawhub.ai is `rafter`. Without this, the first real publish would have failed with an "owner not found" error. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Rome-1
added a commit
that referenced
this pull request
May 10, 2026
Minor bump (not patch) because the betterleaks migration removed user-facing CLI surface — `--with-gitleaks`, `--engine gitleaks`, and `rafter agent update-gitleaks` now hard-error. On a 0.x line, removing documented CLI flags is the textbook MINOR trigger; burying it in a patch would mislead anyone scripting against those flags. Bumps: - node/package.json: 0.7.9 → 0.8.0 - python/pyproject.toml: 0.7.9 → 0.8.0 - node/resources/rafter-security-skill.md: 0.7.9 → 0.8.0 (ClawHub publish) - python/rafter_cli/resources/rafter-security-skill.md: 0.7.9 → 0.8.0 - recipes/openclaw.md example frontmatter: 0.7.9 → 0.8.0 CHANGELOG cleanup: - Move betterleaks bullets from [0.7.9] (where the PR #93 octopus merge parked them under main's `### Changed` heading) into the new [0.8.0] section. The published v0.7.9 (dc81574) does not contain betterleaks code; npm/PyPI 0.7.9 still ships gitleaks. - New [0.8.0] groups all unreleased bullets (rf-hrtd dry-run, ClawHub auto-publish) and adds three Fixed entries: rf-cfjc (action.yml jq parser, fixed in 941879f), #96 (ClawHub owner handle), rf-z6sv (#97, pre-commit rev pin bump). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Rome-1
added a commit
that referenced
this pull request
May 10, 2026
Minor bump (not patch) because the betterleaks migration removed user-facing CLI surface — `--with-gitleaks`, `--engine gitleaks`, and `rafter agent update-gitleaks` now hard-error. On a 0.x line, removing documented CLI flags is the textbook MINOR trigger; burying it in a patch would mislead anyone scripting against those flags. Bumps: - node/package.json: 0.7.9 → 0.8.0 - python/pyproject.toml: 0.7.9 → 0.8.0 - node/resources/rafter-security-skill.md: 0.7.9 → 0.8.0 (ClawHub publish) - python/rafter_cli/resources/rafter-security-skill.md: 0.7.9 → 0.8.0 - recipes/openclaw.md example frontmatter: 0.7.9 → 0.8.0 CHANGELOG cleanup: - Move betterleaks bullets from [0.7.9] (where the PR #93 octopus merge parked them under main's `### Changed` heading) into the new [0.8.0] section. The published v0.7.9 (dc81574) does not contain betterleaks code; npm/PyPI 0.7.9 still ships gitleaks. - New [0.8.0] groups all unreleased bullets (rf-hrtd dry-run, ClawHub auto-publish) and adds three Fixed entries: rf-cfjc (action.yml jq parser, fixed in 941879f), #96 (ClawHub owner handle), rf-z6sv (#97, pre-commit rev pin bump). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
5 tasks
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
1 participant
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.
The actual ClawHub handle is `rafter`, not `raftersecurity`. One-line fix in `publish.yml` so the first real publish doesn't fail with "owner not found."
🤖 Generated with Claude Code