Repository navigation
Releases: Capsize-Games/spikeforge
Release list
spikeforge 0.6.1
Security-hardening patch. Checkpoint loads are fail-closed (weights_only=True everywhere; CheckpointError instead of unpickling, #99). build_topology validates every size-bearing parameter before allocation (#103). The Docker image installs from hashed lockfiles with --no-deps local distributions and a pip check gate (#106). Release PR #138.
spikeforge-targets 0.2.2
Patch release, no code changes: re-released so the 0.6.0 compatibility row is co-installable (the 0.2.1 pin set excluded core 0.6.0). See #97.
spikeforge-server 0.5.0
spikeforge-serve 0.2.5
Patch release, no code changes: re-released so the 0.6.0 compatibility row is co-installable (the 0.2.4 pin set excluded core 0.6.0). See #97.
spikeforge-io 0.1.5
Patch release, no code changes: re-released so the 0.6.0 compatibility row is co-installable (the 0.1.4 pin set excluded core 0.6.0). See #97.
spikeforge-hub 0.5.0
spikeforge 0.6.0
Community hub namespace and account CLI. The hub accepts source: "community" entries with @handle/slug ids and consumes the hosted index with ETag caching; spikeforge-hub login/whoami/push/pull/quota ship, and the server adds the hub_pull/bundle_build WebSocket pairs (protocol 1.1; major-only negotiation keeps 1.0 clients working). Also the topology_params num_classes override fix, the hub entry-module split (no behavior change), the client fork provenance record with a first @capsizellc/commons adoption, and CI automation workflows (inert until their secrets are set).
This tested package combination is recorded in compatibility.json:
| Distribution | Version |
|---|---|
| spikeforge | 0.6.0 |
| spikeforge-targets | 0.2.1 (unchanged) |
| spikeforge-hub | 0.4.0 |
| spikeforge-server | 0.4.0 |
| spikeforge-serve | 0.2.4 (unchanged) |
| spikeforge-io | 0.1.4 (unchanged) |
| spikeforge-clients | 0.1.1 (unchanged) |
Each included change merged with green required CI (plus reruns past the known MNIST-download flake, tracked in #87), and the release workflow verified tag/pyproject/matrix agreement before publishing to PyPI.
spikeforge 0.5.2
Repository roll-up with no core code changes since 0.5.1: upstream tonic report outcomes recorded (#79), CIFAR10-DVS licence verified as CC-BY-4.0 from its figshare record (#80), source-map-js security bump in the client (#74), and a workstation dashboard-deploy script that also stops rsync shipping unread build output (#51).
This tested package combination is recorded in compatibility.json:
| Distribution | Version |
|---|---|
| spikeforge | 0.5.2 |
| spikeforge-targets | 0.2.1 (unchanged) |
| spikeforge-hub | 0.3.2 (unchanged) |
| spikeforge-server | 0.3.4 (unchanged) |
| spikeforge-serve | 0.2.4 (unchanged) |
| spikeforge-io | 0.1.4 (unchanged) |
| spikeforge-clients | 0.1.1 (unchanged) |
Only the core version and the satellite core pins move. The WebSocket protocol remains 1.0.
Each included change merged with green required CI, and the release workflow verified tag/pyproject/matrix agreement before publishing to PyPI.
spikeforge-server 0.4.0
New WebSocket pairs hub_pull/hub_pull_state (pull a community version with progress) and bundle_build/bundle_built (build a saved model into a .spkf), under protocol 1.1 with major-only negotiation. Requires spikeforge~=0.6.0 and spikeforge-hub~=0.4.0.
See the spikeforge 0.6.0 release for the tested combination.
spikeforge-hub 0.4.0
Community namespace: source: "community" entries with @handle/slug ids validate, the hosted index.json loads through the existing catalog validator with ETag caching, and the CLI grows login/whoami/push/pull/quota. The entry module is split into schema and checks with no behavior or import-path change. Requires spikeforge~=0.6.0.
See the spikeforge 0.6.0 release for the tested combination.