feat: TOS release upload + GitHub-free install path for memory plugins#2575
Merged
Conversation
Add a standalone workflow (20. Release TOS Upload) that runs on release publish (or manual dispatch with a tag for backfill) and uploads: - the source archive to releases/<tag>/ and releases/latest/ - both memory-plugin install.sh scripts to versioned paths and to stable root paths for a China-reachable one-liner URL Reuses the existing TOS secrets (AK/SK/region/endpoint) with a new TOS_RELEASE_BUCKET secret so release artifacts stay out of the docs bucket. Missing secrets skip gracefully (fork-friendly); real upload failures fail the workflow.
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
Domestic users can't reach github.com / raw.githubusercontent.com, so the existing one-liner installers stall at their step-3 `git clone`. Add a GitHub-free path that sources everything from Volcengine TOS: - Both install.sh learn OPENVIKING_REPO_ARCHIVE_URL: when set, fetch the source from a zip (curl + unzip) instead of git clone. A .openviking-archive-source marker makes re-runs idempotent and refuses to clobber a git checkout or unrelated data at REPO_DIR. - New setup-helper/tos-install.sh bootstrap per plugin: sets the TOS archive URL, downloads the real install.sh from TOS to a temp file (kept off the stdin pipe so prompts stay interactive), and delegates. - release-tos.yml uploads both tos-install.sh alongside install.sh. One-liner for users behind the GFW: bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/claude-code-memory-plugin/tos-install.sh) The GitHub default path is unchanged; archive mode only activates when OPENVIKING_REPO_ARCHIVE_URL is set.
19 tasks
t0saki
changed the title
Main agent-integration docs (zh/en, claude-code + codex) keep the GitHub one-liner and add the TOS equivalent for regions where GitHub is hard to reach. The CDN integration cards switch their install one-liner to the TOS bootstrap only, since that gallery is served where GitHub raw is unreliable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Two related changes that together give users behind the GFW a stable, GitHub-free way to install the memory plugins.
release-tos.yml): on every published GitHub Release, upload the source zip and both plugins' installers to Volcengine TOS (bucketovrelease), so users who can't reachraw.githubusercontent.comhave a China-reachable mirror — same way the repo already servescli/install.sh.git clone github.com/.... Bothinstall.shnow acceptOPENVIKING_REPO_ARCHIVE_URL(fetch the source from a zip instead of cloning), and a per-plugintos-install.shbootstrap wires the TOS mirror so the whole flow runs without GitHub.China one-liners:
Type of Change
Changes Made
.github/workflows/release-tos.yml(20. Release TOS Upload): triggers onrelease: published(skipscli*tags) or manual dispatch with ataginput for backfills. Reuses the existingTOS_ACCESS_KEY/_SECRET_KEY/_REGION/_ENDPOINTsecrets plus a newTOS_RELEASE_BUCKET. Uploads to versionedreleases/<tag>/(immutable) and stable root paths (no-cache); the stable zip is a server-sideCopyObjectfrom the versioned key rather than a second cross-border upload. Missing secrets skip gracefully (fork-friendly); real upload errors fail the run.setup-helper/install.shlearnOPENVIKING_REPO_ARCHIVE_URL: when set, step 3 fetches + unzips the source instead ofgit clone. A.openviking-archive-sourcemarker keeps re-runs idempotent and refuses to clobber a git checkout or unrelated data atREPO_DIR. The GitHub default path is unchanged.setup-helper/tos-install.shper plugin: defaults the archive URL to the TOSlatestzip, downloads the realinstall.shto a temp file (off the stdin pipe, so prompts stay interactive), and delegates.OPENVIKING_TOS_BASEoverrides the mirror.Testing
actionlintclean. The workflow was exercised on this repo via a temporary branch-scoped push trigger (only20. Release TOS Uploadfired — no other workflows, no tags created): it checked out the branch tip, built the zip, and uploaded the source zip + bothinstall.sh+ bothtos-install.shto TOS, with the server-side copy for the stable zip.Real end-to-end, against live TOS with zero GitHub access (sandboxed
env -i+ tempHOME, noclaude/codexon PATH):bash <(curl -fsSL .../claude-code-memory-plugin/tos-install.sh)→ downloads the installer + source zip from TOS, lays out the tree (sentinel present,.gitabsent), adds the rc source-hook, preserves existingovcli.conf. Idempotent on re-run; a pre-existing non-sentinelREPO_DIRis refused with its contents intact.bash <(curl -fsSL .../codex-memory-plugin/tos-install.sh)→ same source path, then builds the marketplace + plugin cache, setsenabled = true+plugin_hooks = trueinconfig.toml, and renders the/mcpURL into.mcp.json.Checklist
Additional Notes
Requires a
TOS_RELEASE_BUCKETrepo secret (already configured =ovrelease). Updating the README / docs one-liners to point at the TOS bootstrap is intentionally a follow-up, once the path has run through a real release.wrapper.shand friends are not uploaded separately — they ship inside the source zip.