Skip to content

fix(toolchain,ci): pack agent bin at real entry file; fix crates.io base-filesystem path#267

Open
NathanFlurry wants to merge 1 commit into
mainfrom
fix/agent-pack-real-entry-and-crates-fixture-path
Open

fix(toolchain,ci): pack agent bin at real entry file; fix crates.io base-filesystem path#267
NathanFlurry wants to merge 1 commit into
mainfrom
fix/agent-pack-real-entry-and-crates-fixture-path

Conversation

@NathanFlurry

Copy link
Copy Markdown
Member
  • Pack agent commands to point package.json bin at the real entry file in the packed closure instead of a bin/<cmd> symlink. npm/pnpm publish drop symlinks, so published agent packages lost their bin/ entrypoints and the sidecar could not project the ACP adapter (it resolved to /unknown/<cmd> at runtime). This matches the sidecar's documented contract (a shipped package must not rely on bin/ symlinks; commands come from the bin map → real entry file).
  • Fix the crates.io publish job's staging step: it copied packages/core/fixtures/base-filesystem.json, which no longer exists, breaking the job. The single committed copy lives at crates/vfs/assets/base-filesystem.json.

@railway-app

railway-app Bot commented Jul 4, 2026

Copy link
Copy Markdown

🚅 Environment secure-exec-pr-267 in rivet-frontend has no services deployed.


🚅 Deployed to the secure-exec-pr-267 environment in secure-exec

Service Status Web Updated (UTC)
secure-exec 😴 Sleeping (View Logs) Web Jul 4, 2026 at 10:27 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant