Releases: DeanoC/Spiderweb
Releases · DeanoC/Spiderweb
Release list
v0.5.7
Highlights
Native macOS SpiderApp Support
- Fixed Spiderweb’s workspace-capability routing so the new native macOS SpiderApp can load packages, binds, and terminal capabilities through the same shared-core backend path as the CLI.
- Corrected local capability binding resolution and stale bind refresh behavior so workspace aliases track the real local venom directories instead of getting stuck on outdated short names.
Native Terminal Routing
- Fixed terminal venom namespace seeding and control-file routing so native SpiderApp terminal exec reaches the real local terminal service instead of dead-ending on missing or misrouted control files.
- Added explicit host-versus-workspace shell support in the terminal backend so SpiderApp can steer agents and users into the correct execution root.
macOS Runtime Packaging
- Hardened the signed macOS release path around the bundled native SpiderApp/Spiderweb tools, including notarized package validation for the updated suite packaging flow.
- Fixed the macOS terminal runtime to avoid assuming GNU
timeoutis present on user machines.
What's Changed
Full Changelog: v0.5.6...v0.5.7
v0.5.6
v0.5.5
What's Changed
- Prepare Spiderweb 0.5.4 release by @DeanoC in #188
- Default Spiderweb to hosted venom registry by @DeanoC in #189
- Add explicit registry channel policy controls by @DeanoC in #190
- Add explicit package update operation by @DeanoC in #191
- Add package release history metadata by @DeanoC in #192
- Add batch package update operation by @DeanoC in #193
- Bump Spiderweb to 0.5.5 by @DeanoC in #194
Full Changelog: v0.5.4...v0.5.5
v0.5.4
What's Changed
- Release Spiderweb 0.5.1 by @DeanoC in #179
- Pin SpiderVenoms 0.5.3 and validate release checksums by @DeanoC in #180
- Move runtime-only code out of src/venoms by @DeanoC in #181
- Fix installer fallback and version bump workflow by @DeanoC in #182
- Verify signed SpiderVenoms bundles and pin v0.5.6 by @DeanoC in #183
- Add explicit venom release rollback operation by @DeanoC in #184
- Add negative tests for managed bundle validation by @DeanoC in #185
- Move terminal and git namespace code into runtime by @DeanoC in #186
- Add explicit venom release switch surface by @DeanoC in #187
Full Changelog: v0.5.1...v0.5.4
v0.5.1
What's Changed
- Align macOS release version with v0.3.1 by @DeanoC in #159
- Release v0.3.2 by @DeanoC in #161
- Windows shared mount helper, workspace cleanup, and 0.3.2 prep by @DeanoC in #160
- Split Spiderweb host core from local node by @DeanoC in #162
- Bound mount graph file read materialization by @DeanoC in #163
- Add FusePathCache two-level cache to WinFSP for FSKit perf parity by @DeanoC in #164
- Unify namespace mount path and external agent E2E by @DeanoC in #165
- Finish Spiderweb legacy cleanup and workspace rename by @DeanoC in #166
- chore: bump submodules by @DeanoC in #167
- fix: use the shared bound proxy rewrite path on Windows by @DeanoC in #168
- chore: bump SpiderNode by @DeanoC in #169
- Hard-cut canonical venom workspace contract by @DeanoC in #170
- Finish Spiderweb venom hard-cut cleanup by @DeanoC in #171
- Add Spiderweb package lifecycle and mount fixes by @DeanoC in #172
- Hard-cut final public venom surface by @DeanoC in #173
- Harden canonical git and search_code venoms by @DeanoC in #174
- Wire macOS computer and browser venoms through Spiderweb by @DeanoC in #175
- Sync hardened macOS computer driver by @DeanoC in #176
- feat: add spiderweb-mcp-bridge for MCP venom support by @DeanoC in #177
- Wire cross-platform computer browser targets by @DeanoC in #178
Full Changelog: v0.3.2...v0.5.1
Spiderweb v0.3.2
Highlights
- fixed remote workspace and mount endpoint advertisement so routed
/v2/fsURLs no longer leak127.0.0.1to other machines - verified the fix with a real remote Windows WinFsp namespace smoke against
ws://192.168.10.101:18790/, including routed reads, routed writes, and OS mount creation - shipped a refreshed notarized macOS installer with the self-contained filesystem repair path and LAN-reachable service defaults
Assets
Spiderweb-macos-0.3.2.pkg: notarized macOS installerSpiderweb-macos-0.3.2.pkg.sha256: SHA-256 for the macOS installer
Notes
- source archives for
v0.3.2include the server-side remote endpoint fix - the existing Linux release tarball remains on
v0.3.1for now
Spiderweb v0.3.1
Spiderweb v0.3.1
This release closes the strict external-agent machine-independence milestone for the Linux installer-first Spiderweb + external Codex end-to-end path.
Highlights:
- namespace-backed terminal execution sees the same mounted namespace as the agent
- mounted venom control writes now commit on close for normal append/close behavior
- bridge-runtime helper shims and reporting fixes remove false host-runtime leakage in strict runs
- the strict external-agent live path now reaches:
reliability_ok=trueworkspace_bootstrap_ok=truemachine_independence_ok=true
Linux release asset:
spiderweb-linux-x86_64.tar.gzspiderweb-linux-x86_64.tar.gz.sha256
macOS release asset refresh on 2026-03-19:
- replaced
Spiderweb-macos-0.3.1.pkgwith a notarized and stapled installer built from commit255c0c364736 - fixes packaged FSKit filesystem reinstall and the duplicated
AGENTS.mdcontract heading issue - includes
Spiderweb-macos-0.3.1.pkg.sha256
Spiderweb v0.3.0
Spiderweb v0.3.0
First published Linux binary release for Spiderweb.
Highlights:
- installer-first Spiderweb host workflow
- external Codex workspace E2E harness
- agent-driven workspace bootstrap metadata and quick reference
- release-archive installer path for faster repeatability runs
Included Linux binaries:
spiderwebspiderweb-configspiderweb-controlspiderweb-fs-mountspiderweb-fs-node
Assets:
spiderweb-linux-x86_64.tar.gzspiderweb-linux-x86_64.tar.gz.sha256