Skills 2026-08-04 21:39 UTC
tensorlake-skillsv3.0.0
Version [3.0.0] committed by 匿名贡献者. Update Category: Routine Updates & Maintenance. Commit details: Sw/update (#57). This update performs routine maintenance and minor adjustments.
CommitRaw commit message
Sw/update (#57) * release: v3.0.0 — re-verify all references against current docs (SDK 0.5.97) Full re-verification of every reference file against the live docs. Two product areas were added upstream (Cloud Volumes, Git repositories) and two were removed (Document Ingestion, integrations), so this is a breaking restructure of references/. Added: - references/volumes_and_git.md — Cloud Volumes (tl fs, FilesystemClient) and managed Git repositories (tl git, RepositoryClient): mounts, autosave/snapshots, sessions, concurrent-write semantics, workspaces, promote/rebase, server-side merges, and the shared architecture. - Sandbox pools, tl sbx copy, retained process logs, the tl-user default user/working directory, Tensorlake managed images, --docker_compat, public application endpoints (allow=["unauthenticated_requests"], HttpBody, ctx.headers), and the OpenCode / Crabbox / Devin Outposts integrations. Corrected (previously asserted, not supported by current docs): - SandboxClient is not deprecated — it is the documented API for pools, log queries, and expose_ports/unexpose_ports. - allow_out narrows egress even when allow_internet_access is true. - tl sbx clone replaced by tl sbx copy, with different semantics. - checkpoint() takes checkpoint_type; dropped undocumented wait=False and the unverified SnapshotType import path. - /workspace is root-owned on managed images; dropped secret_names from Sandbox.create(). - Progress updates are a polling endpoint, not SSE. Removed: references/integrations.md and all document-ingestion content (parse-job polling, TEDS/JSON-F1 benchmarks, documentai webhook events, tensorlake.documentai examples, Playground) — deleted upstream. Also updated sources.yaml, check_drift.py routing, feature_lookup.md, README.md, and evals/filter.py. SDK version 0.5.97, last verified 2026-08-04 across all nine reference files. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix: correct allow_out / DNS semantics in sandbox networking (v3.0.1) The docs page claims a non-empty `allow_out` allows the listed destinations "and DNS". Live sandbox tests show DNS stays blocked when `allow_internet_access=False`, even with a non-empty `allow_out` — so a domain entry can never resolve and every request fails with `Could not resolve host`. Verified against SDK 0.5.97 with one sandbox per config: - `allow_internet_access=False, allow_out=["example.com"]` → all blocked - `allow_internet_access=False, allow_out=["1.1.1.1"]` → 1.1.1.1 reachable - `allow_internet_access=True, allow_out=["example.com"]` → example.com only - `allow_out=["1.1.1.1"] + deny_out=["1.0.0.0/8"]` → allow wins Also flags that the SDK's own `NetworkConfig` docstring is wrong: it says internet-on means all traffic is allowed unless denied, implying `allow_out` is a no-op with internet on. It narrows egress in both modes. references/sandbox_sdk.md: parameter table rewritten, examples split into a domain allowlist and an IP/CIDR-only strict form, allow_out-beats-deny_out documented, plus an 8-row verified behavior matrix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>