Skip to content

fix(ci): skills sync steps past the five hidden ClawHub versions blocking it - #6713

Merged
miguel-heygen merged 2 commits into
mainfrom
fix/clawhub-sync-taken-versions
Oct 29, 2026
Merged

miguel-heygen merged 2 commits into
mainfrom
fix/clawhub-sync-taken-versions

Conversation

@miguel-heygen

@miguel-heygen miguel-heygen commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

The "Sync skills to ClawHub" workflow has failed on every run since at least 2026-10-27. Five skills (hyperframes, hyperframes-cli, hyperframes-registry, media-use, remotion-to-hyperframes) fail with Version X already exists, so no skill update has reached ClawHub for about two days.

Cause

For each of the five, the registry holds one more version than latest points to (hyperframes: 51 versions, latest 1.0.50; inspect --version 1.0.51 answers "Version not found"). That version is stored but unlisted, so clawhub sync --bump patch keeps bumping from latest to the same taken version.

Why the registry hides them is unknown. A hidden version cannot be read, and nothing in the logs says why. Each one is listed below because it is the exact version the failing run reports as taken; no other evidence is behind the listing.

Fix

SKIPPABLE_TAKEN (from #5081) gains the five taken versions:

skill taken published instead
hyperframes 1.0.51 1.0.52
hyperframes-cli 1.0.73 1.0.74
hyperframes-registry 1.0.15 1.0.16
media-use 1.0.87 1.0.88
remotion-to-hyperframes 1.0.17 1.0.18

The behaviour stays as #5081 designed it: only these exact versions are stepped past, one patch, and the job fails unless the registry's latest is the version it published. Any other taken version, on any skill, still fails the run so a person looks.

fails without the fix: publishes one patch past each acknowledged taken version

Tests

scripts/clawhub-sync.test.mjs adds a case replaying the five failures. Against main's script it fails; with this change all 11 tests pass, and the format check is clean.

After merge: a dry-run dispatch first, then a real run.

@heygengenesis heygengenesis Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: REQUEST CHANGES · 1 blocker · 1 important · 0 nits · head 199aef32

  • blocker: this is a fix PR, and its body has no fails without the fix: line naming a test that fails without the fix. That line is required for this lane. I checked locally that the three new tests fail against main's script (8 pass, 3 fail) and that all 11 pass at the head. So the line could read, for example: fails without the fix: steps past a taken version for any skill, not one hard-coded.
  • important: ↓ inline. This reverses a decision #5081 made on purpose, and the body does not say why.
Scope

Read scripts/clawhub-sync.mjs and its test end to end. The loop, the bound and the latest check look right. The workflow has concurrency: clawhub-sync, so two runs do not race for the same version. CI: green except Windows render verification, which is still running.

Comment thread scripts/clawhub-sync.mjs Outdated
@miguel-heygen miguel-heygen changed the title fix(ci): skills sync steps past any taken ClawHub version, not one hard-coded skill fix(ci): skills sync steps past the five hidden ClawHub versions blocking it Oct 29, 2026

@heygengenesis heygengenesis Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE · 2 resolved, 0 open, 0 new · 199aef3 → b88777e

The fails without the fix: test fails on main's script (10 pass, 1 fail), and all 11 pass at the head. The five allowlisted versions match main's latest sync failure. CI is green.

@miguel-heygen
miguel-heygen added this pull request to the merge queue Oct 29, 2026
Merged via the queue into main with commit 49e0312 Oct 29, 2026
105 of 106 checks passed
@miguel-heygen
miguel-heygen deleted the fix/clawhub-sync-taken-versions branch October 29, 2026 05:45
@heygengenesis heygengenesis Bot mentioned this pull request Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant