fix(ci): drop the pyodide staging from agent-os release-assets#1544
Merged
Conversation
Member
Author
|
Stack for rivet-dev/agentos
Get stack: |
railway-app
Bot
temporarily deployed
to
rivet-frontend / agentos-pr-1544
The 'Stage release assets' step copied pyodide assets from crates/execution/assets/pyodide — a secure-exec-only path that does not exist in agent-os — so cp failed with exit 1 on every release (0.2.1, 0.2.2) and now, reproducibly, on a preview publish: cp: cannot stat 'crates/execution/assets/pyodide/pyodide.asm.wasm': No such file agent-os builds against the published secure-exec execution crate, whose build.rs stages zero-byte pyodide placeholders (guest Python disabled, 'no CDN dependency') and nothing in agent-os fetches pyodide from its own release/R2. The block was vestigial copy-paste from secure-exec's publish.yaml. agent-os releases host only the platform sidecar binaries; pyodide is hosted by secure-exec's release. Combined with running the staging step on previews (prior commit), this class of bug now surfaces pre-release instead of only at release time.
NathanFlurry
changed the title
NathanFlurry
force-pushed
the
stack/ci-publish-run-release-assets-staging-on-previews-reproduce-guard-the-pyodide-staging-bug-qypsznwp
branch
from
5ece02c to
3f96afd
Compare
railway-app
Bot
temporarily deployed
to
rivet-frontend / agentos-pr-1544
NathanFlurry
deleted the
stack/ci-publish-run-release-assets-staging-on-previews-reproduce-guard-the-pyodide-staging-bug-qypsznwp
branch
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5328
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5338
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5324
railway-app
Bot
requested a deployment
to
rivet-frontend / secure-exec-pr-112
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5320
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5333
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5314
railway-app
Bot
requested a deployment
to
rivet-frontend / secure-exec-pr-121
railway-app
Bot
requested a deployment
to
rivet-frontend / secure-exec-pr-111
railway-app
Bot
requested a deployment
to
rivet-frontend / secure-exec-pr-119
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.
The 'Stage release assets' step copied pyodide assets from
crates/execution/assets/pyodide — a secure-exec-only path that does not exist in
agent-os — so cp failed with exit 1 on every release (0.2.1, 0.2.2) and now,
reproducibly, on a preview publish:
cp: cannot stat 'crates/execution/assets/pyodide/pyodide.asm.wasm': No such file
agent-os builds against the published secure-exec execution crate, whose build.rs
stages zero-byte pyodide placeholders (guest Python disabled, 'no CDN dependency')
and nothing in agent-os fetches pyodide from its own release/R2. The block was
vestigial copy-paste from secure-exec's publish.yaml. agent-os releases host only
the platform sidecar binaries; pyodide is hosted by secure-exec's release.
Combined with running the staging step on previews (prior commit), this class of
bug now surfaces pre-release instead of only at release time.