Skip to content

ci: add trusted ClawHub publishing - #26

Merged
rjcloudsigma merged 1 commit into
mainfrom
chore/clawhub-trusted-publish-20260829
Aug 29, 2026
Merged

ci: add trusted ClawHub publishing#26
rjcloudsigma merged 1 commit into
mainfrom
chore/clawhub-trusted-publish-20260829

Conversation

@rjcloudsigma

Copy link
Copy Markdown
Collaborator

Summary

Add a trusted GitHub OIDC ClawHub publication workflow for the legacy optimizer migration release.

The workflow:

  • uses the clawhub-publish GitHub environment;
  • requests only contents: read and id-token: write;
  • runs install, tests, build, and ClawHub validation before publishing;
  • derives the package owner from the trusted binding rather than overriding it;
  • pins source ref and source commit to the exact authorized ${{ github.sha }};
  • defaults to source version 0.12.0 and the latest tag.

Verification

  • typecheck passed
  • smoke passed
  • 43 Node tests passed
  • build passed
  • ClawHub validation passed with zero warnings/issues
  • git diff --check passed

One-time external prerequisite

After merge, a CloudSigma ClawHub organization owner must configure the trusted publisher for:

  • package: @cloudsigma/openclaw-token-cache-optimizer
  • repository: cloudsigma/openclaw-token-cache-optimizer
  • workflow: publish-clawhub.yml
  • environment: clawhub-publish

No long-lived ClawHub token or GitHub secret is required after that binding.

@rjcloudsigma
rjcloudsigma merged commit 4e7a211 into main Aug 29, 2026
1 check passed
@rjcloudsigma
rjcloudsigma deleted the chore/clawhub-trusted-publish-20260829 branch August 29, 2026 16:29
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.

2 participants