You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor to install from npm instead of building from git (#15)
* Refactor to install from npm instead of building from git
* Bump openclaw upstream to 2026.3.2
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* ci: use dappnodesdk bump-upstream and add Pinata secrets for IPFS hash comments
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* ci: remove build-test job from main.yml, rely on bump-upstream for hash comments
Hash comments are posted by auto_check.yml via dappnodesdk bump-upstream.
The build-test job was causing ENOTFOUND failures on the ipfs-dev-gateway runner.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* ci: restore build-test job for PR checks using working build command
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* ci: add build-hash job on ubuntu-latest for IPFS hash comments on all PRs
Separates concerns:
- build-test: ipfs-dev-gateway, PR events only, verifies Docker build
- build-hash: ubuntu-latest, push to non-main branches, posts IPFS hash via Pinata
- release: ipfs-dev-gateway, push to main only
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Fix CI: use github-action build for IPFS hash comments on PRs
- Remove build-test job (build-hash serves as both test and hash poster)
- Remove pull_request trigger (only push events needed)
- Fix command: 'github-action build' instead of 'build github-action build'
(the wrong command was calling the build subcommand with provider defaulting
to dappnode, causing ENOTFOUND errors; the correct subcommand uses Pinata)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
0 commit comments