ci: upload source zip and plugin installers to TOS on release#2575
Open
t0saki wants to merge 2 commits into
Open
ci: upload source zip and plugin installers to TOS on release#2575t0saki wants to merge 2 commits into
t0saki wants to merge 2 commits into
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. |
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
1 participant
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
Add a standalone workflow (
20. Release TOS Upload) that uploads the source archive and both memory-plugin installers to TOS whenever a GitHub Release is published. This gives users in regions whereraw.githubusercontent.comis unreachable a stable, China-accessible one-liner install URL, plus a mirrored source zip (the repo already serves the CLI installer this way via TOS).Object layout per release:
releases/<tag>/openviking-<tag>-source.zipreleases/<tag>/{claude-code,codex}-memory-plugin/install.shreleases/latest/openviking-source.zip{claude-code,codex}-memory-plugin/install.shRelated Issue
N/A
Type of Change
Changes Made
.github/workflows/release-tos.yml, triggered onrelease: published(skipscli*tags) or manual dispatch with ataginput for backfilling historical releases.TOS_ACCESS_KEY/TOS_SECRET_KEY/TOS_REGION/TOS_ENDPOINTsecrets with a newTOS_RELEASE_BUCKETsecret (already configured), keeping release artifacts out of the docs bucket; uploads via the same AWS CLI S3-compatible pattern asdocs-tos.yml.releases/latestzip is produced by a server-sideCopyObjectfrom the versioned key instead of re-transferring ~74MB over the slow runner-to-TOS route (measured: 16s copy vs ~10min re-upload).update_latestdispatch input allows backfilling an old tag without overwriting the stable/latest paths.Testing
End-to-end validated on this repository via a temporary test branch with a branch-scoped push trigger (no other workflows fired, no tags created): all six objects uploaded for
v0.3.24with correct content-type / cache-control, the server-side copy completed in 16s, and the missing-secrets skip path was exercised beforeTOS_RELEASE_BUCKETexisted.actionlintpasses.Checklist
Screenshots (if applicable)
N/A
Additional Notes
Switching the README / docs one-liner URLs to the TOS-hosted installers is intentionally left to a follow-up PR once the links have been confirmed stable.