v0.2.0¶
Release Date: 2026-10-23
SystemSpec Deploy v0.2.0 moves the project to its new name and Go module path, github.com/plexusone/systemspec-deploy. It is the deployment topology specification of the SystemSpec family: what runs where, its images, ports and connections, and the cloud resources it uses.
This is a breaking change release for Go SDK users, because import paths change. The document format, the CLI and the graphize provider are unchanged, so existing system.json files work as before.
Highlights¶
- Breaking: the Go module path is now
github.com/plexusone/systemspec-deploy - Same format: existing system spec documents validate and render without changes
- Same CLI: the
system-speccommand and its subcommands are unchanged; only the install path moves
Breaking Changes¶
Go module path¶
Before (v0.1.0):
import (
"github.com/plexusone/system-spec/spec"
"github.com/plexusone/system-spec/graph"
"github.com/plexusone/system-spec/render"
)
After (v0.2.0):
import (
"github.com/plexusone/systemspec-deploy/spec"
"github.com/plexusone/systemspec-deploy/graph"
"github.com/plexusone/systemspec-deploy/render"
)
Package names, types and functions are the same. Only the module path changes.
Graphize provider import¶
Before (v0.1.0):
After (v0.2.0):
The provider still registers under the name system-spec and produces the same node and edge IDs, so existing graphs stay valid.
JSON Schema $id¶
The generated schema's $id is now:
Tools that match the schema by $id need the new value. The schema's structure is unchanged.
Installation¶
# CLI
go install github.com/plexusone/systemspec-deploy/cmd/[email protected]
# Go SDK
go get github.com/plexusone/[email protected]
See the migration guide for step-by-step instructions.
Dependencies¶
- Upgraded
github.com/invopop/jsonschemafrom v0.13.0 to v0.14.0. The generated JSON Schema is unchanged.
Documentation¶
- Updated the README, MkDocs site and SDK guides for the new module path and repository
- Added a migration guide