Skip to content

RTVision T3 Code 0.0.106

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Nov 10:36
v0.0.106
e87db68
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

RTVision T3 Code 0.0.106 integrates 49 upstream commits through 337c5858c33bc7f8f6dfd391a2c279fa0f7e4d17.

  • Adds MCP Apps for Claude tool calls, structured requests for secrets, and optional host/owner/repo clone folders.
  • Fixes stopped-run history loss, pending questions, completion wakeups, branch divergence refresh and provider usage-limit recovery.
  • Improves T3 Connect reconnects, large configuration transfers on slow links, thread stream recovery and access settings across environments.
  • Saves pull request description checkbox edits on web and mobile. Fixes mobile keyboard/autocorrect behavior, Claude account settings, and image/video previews.

Adopts upstream error/environment/crypto refactors and pull request description readback. Retains RTVision Gitea integration, Vim/editor controls, permission rechecks, rollback/database protections, registry/update routing, Node/npm/OpenRC and Alpine support, and release packaging. Keeps ffi-rs 1.3.7 with correctly labeled musl binaries. Alpine typechecks use Effect's Go compiler because upstream's packaged tsrs requires glibc; supported platforms retain tsrs.

Merged PR: #121
Source: e87db68fdbfeeae0aae37825d9b25eac35a94527, with the exact tree approved as b1e7a36419611aae790d67a9a0eb40c4e406f537. Primary and independent GPT-6 Astra source reviews passed under the maintainer-authorized large-diff fallback. CodeRabbit explicitly skipped 608 files exceeding its 100-file limit. Applicable PR CI passed, including full web/browser coverage and all server shards.

Windows and Linux x64 desktop installers are unsigned. Node/npm installations use https://npm-registry.rtvision.com/. No live service deployment or restart is part of this release.

Validation: merged-head CI and release builds passed at the exact source SHA. All ten expected assets passed SHA256SUMS, and updater SHA-512 hashes match the installers. The npm tarball's registry version and integrity match. A clean plain-npm installation with npm_config_build_from_source=true passed on Alpine x64; preflight returned ready for 0.0.106 and actual t3 serve returned HTTP 200 with the T3 Code title and no missing-module/native-load errors.

The first Windows archive smoke attempt timed out waiting for HTTP readiness. The unchanged failed job passed its original --version and HTTP serve gate on one rerun; the final release workflow succeeded. The focused model eval was unavailable because this host lacks its vibeproxy provider configuration.

Normal npm version lookup and self-update alias resolution also confirm 0.0.106 and its exact integrity after registry metadata caches refreshed.

Assets 13
Loading