prod-code releases

9 releases from 2026-11-06 to 2026-11-16, 283 downloads of release files.

v0.3.61latest

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.60

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.59

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.58

Fixed

  • code_symbols Lists a Swift Declaration Whose Name the Root Project Also Declares (crates/prod-code-mcp, #2014): in a C, Go or JavaScript checkout with a Swift package inside it, prod-code symbols applyTheme listed only the root's applyTheme and not the Swift method of that name in extension Demo.SurfaceView, and code_definition resolved to the root's alone. A match in the root ended the search before the nested projects were looked at, and sourcekit-lsp, with no build index, answers workspace/symbol with nothing. After a root match the checkout's Swift files that declare the name are now outlined too (a walk with no query when none does), so both are listed and code_definition reports the two candidates. The note for a Swift declaration the analyzer sees but does not list no longer blames "an item inside a function body"; it says sourcekit-lsp lists workspace symbols only with a build index. A scripted-gateway test fails without the change.
  • Enclosing-Symbol Labels Ignore Declarations and Braces Inside Literals and Comments (crates/prod-code-mcp, #2013): the [in ...] label on each hit of code_references, code_grep and other tools named a Rust test in tools/references/tests.rs as GhosttyTerminalNSView::multi_target_deadline_honors_short_budget_and_caps_long_budget. An earlier test writes Swift source into a string ("final class GhosttyTerminalNSView: NSView {",), and the brace-scope scan read it as a class declaration and an open brace. The scan now reads lines whose string and character literals (escapes, multi-line strings, Swift and Python """, Rust raw strings, backticks) and block comments are blanked, with columns unchanged; lifetimes are left as they are. Four tests pin it.
  • code_exec Carries Its Output and Exit Status in structuredContent Too (crates/prod-code-mcp, #2009): in a checkout where sync left out a file under a data directory, code_exec returned the command's output and exit status in its text and, beside it, a structuredContent that held only sync_omitted. A host that shows the structured channel in place of the text showed {"sync_omitted":[...]} and nothing of the command, for echo ok and for a test run alike. Whenever the structured channel is sent, it now also holds exit_code, timed_out, error (when the command did not start), output and output_bytes; the text is unchanged. The test for #1836 checks the new members and fails without the change.
  • Swift References Find the Uses in the Declaring File When a Cold Server Took the Budget (crates/prod-code-mcp, #2008): code_references for a private static func of a Swift type in a fresh worktree answered No references found after about 30 s, while the same file called the method. The 8 s budget of the multi-target scan counts from the start of the call, and a cold sourcekit-lsp took all of it on its first answer, so the scan started with none left and never read the declaring file. The declaring Swift file is now read even then and its uses recorded from the text, as they already were when there was time (#1135); the scan also reads the declaring file first and the files beside it next, so a common name written in many earlier files does not spend the budget first. The answer still says it is partial. Measured on a real checkout: before, No references found; after, the call is listed. Three tests pin it; one fails without the change.
  • A Batch Lookup That Ran Out of Its Share Is Asked Again With the Time the Others Left (crates/prod-code-mcp, #2006): code_definition with symbols and budget_ms: 12000 in a fresh sibling worktree answered the first of three Swift members with did not finish within 3999 ms, while the other two answered at once and most of the budget went unused. The first lookup in a checkout pays for the sync and the server's start, which the rest then share, and each symbol was held to an even share. A symbol that ran out of its share is now asked once more with what is left of the budget when the others have answered; a slow lookup still cannot spend the others' shares (#1168), and a batch still ends within its budget. Two tests pin it.

Changed

  • Hosted CI Warms Mitts's CAS and Scopes Pull-Request Shards (.github/workflows/ci.yml, scripts/ci, #2004): plan previously saved mitts-cache-* right after mitts fetch --locked, locking out compiled ac/ and cas/ entries so 50 shards cold-compiled the workspace across 7 waves even on version-only pull requests. Hosted CI now warms and bounds Mitts's persistent CAS (mitts gc), caches pinned test language tools, prefers mitts in source-building integration test helpers, sizes shards to 16 targets at max-parallel: 16, skips compilation on docs-only changes, runs a fast build_fingerprint smoke check on verified workspace-only version bumps, and narrows pull-request shards to affected workspace packages while keeping full matrix runs on code pushes to main.

Native client and gateway binaries for Linux x86_64, Linux ARM64 and macOS ARM64. macOS binaries are Developer ID signed and Apple notarized. Verify all six binaries against SHA256SUMS.

v0.3.57

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.56

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.55

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.54

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

v0.3.53

Native client and gateway builds. macOS binaries are Developer ID signed and Apple notarized. Verify the six binaries using SHA256SUMS.

Release history from GitHub as of 2026-11-16.