fix(release): ship the automation runtime (sdk/automate/analyze) in release archives - #98
Merged
Merged
Conversation
…mation runtime ships Every release tarball since the automation runtime landed has shipped without sdk/, automate/ and analyze/: build-release.sh stages them only when it can run `pnpm ... build`, and the release job never installed pnpm or the workspace, so the stage skipped with a one-line note nobody read. v3.9.13 and v3.10.0 both have zero sdk/ entries, which is why `tron mcp`, `tron analyze`, `tron run` and now `tron automate` all answered "This TronBrowser build lacks ... Run: tron upgrade" on a fresh install. - release.yml: corepack + `pnpm install --frozen-lockfile --filter @tronbrowser/sdk...` before packaging on linux/macos, and a step that fails the job when the archive has no sdk/automate-bin.js. - build-release.sh: keep the staging build log and print its tail on failure. - services/api mcp/tron: the GET health reply reports the caller's scheme (x-forwarded-proto) instead of http:// behind Railway's TLS edge. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018WGZpo8on6XLGYnccXV3dP
ThreatCrush Security Scan51 finding(s) MEDIUM: 32 | LOW: 19
…and 1 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Release tarballs v3.9.13 and v3.10.0 contain no
sdk/at all:build-release.shstages the automation runtime only whenpnpm ... buildsucceeds, and the release job never installed pnpm or the workspace, so the stage was silently skipped. That is whytron mcp,tron analyze,tron runand nowtron automateanswer "This TronBrowser build lacks ... Run: tron upgrade" on a fresh install.--filter @tronbrowser/sdk...) before packaging on linux/macos.sdk/automate-bin.js.Verified locally:
build-release.sh v3.10.1-test linuxwith pnpm present stages 67sdk/entries includingsdk/automate-bin.js. Tag v3.10.1 after merge.🤖 Generated with Claude Code
https://claude.ai/code/session_018WGZpo8on6XLGYnccXV3dP