chore: bump openclaw to 2026.7.1 (#76)

* chore: bump openclaw upstream to 2026.7.1

* chore: set UPSTREAM_VERSION to 2026.7.1

* fix: address OpenClaw runtime warnings

* fix + feat: Fix config and add nexus login

---------

Co-authored-by: tropibot[bot] <285933081+tropibot[bot]@users.noreply.github.com>
Co-authored-by: hcastc00 <[email protected]>

Merge pull request #72 from dappnode/tropibot/bump-openclaw-v2026.6.11

chore: bump openclaw to 2026.6.11

Merge pull request #68 from dappnode/dappnodebot/bump-upstream/opencl…

…aw/[email protected]

bump openclaw/openclaw to v2026.6.5

Upgrade GitHub Actions to use version 6

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 <[email protected]>

* ci: use dappnodesdk bump-upstream and add Pinata secrets for IPFS hash comments

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

* 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 <[email protected]>

* ci: restore build-test job for PR checks using working build command

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

* 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 <[email protected]>

* 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 <[email protected]>

---------

Co-authored-by: Claude Sonnet 4.6 <[email protected]>