Skip to content

fix(setup-helper): add GitHub API fallback for plugin fetches#1157

Closed
qin-ctx wants to merge 1 commit intomainfrom
fix/setup-helper-github-fallback
Closed

fix(setup-helper): add GitHub API fallback for plugin fetches#1157
qin-ctx wants to merge 1 commit intomainfrom
fix/setup-helper-github-fallback

Conversation

@qin-ctx
Copy link
Copy Markdown
Collaborator

@qin-ctx qin-ctx commented Apr 1, 2026

Description

Improve the OpenClaw setup helper so plugin manifest lookup and plugin file downloads no longer depend solely on raw.githubusercontent.com.

Related Issue

Fixes #1150

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test update

Changes Made

  • add shared helpers for GitHub raw fetches, GitHub Contents API fallback, and timeout handling in the setup helper
  • use the fallback path when resolving plugin manifests, probing plugin directories, and reading fallback package metadata
  • route plugin file downloads through the same fallback so installs can continue when raw.githubusercontent.com is blocked but GitHub API access still works

Testing

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have tested this on the following platforms:
    • Linux
    • macOS
    • Windows

Manual checks:

  • node --check examples/openclaw-plugin/setup-helper/install.js
  • verified that v0.3.2 contains examples/openclaw-plugin/install-manifest.json and index.ts, so the reported failure is due to remote file access rather than a missing tag asset

Checklist

  • My code follows the project's coding style
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

Screenshots (if applicable)

N/A

Additional Notes

This keeps the failure mode explicit: the helper warns when raw.githubusercontent.com is unavailable and only succeeds if the same file can be fetched via the GitHub Contents API. A new npm release of openclaw-openviking-setup-helper is still required before ov-install users receive the fix.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Failed to generate code suggestions for PR

@qin-ctx qin-ctx closed this Apr 2, 2026
@github-project-automation github-project-automation bot moved this from Backlog to Done in OpenViking project Apr 2, 2026
@qin-ctx qin-ctx deleted the fix/setup-helper-github-fallback branch April 2, 2026 09:18
@qin-ctx qin-ctx restored the fix/setup-helper-github-fallback branch April 2, 2026 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[Bug]: openclaw-openviking-setup-helper安装插件报错

1 participant