GOWDK v0.2.0
Pre-release
Pre-release
Experimental 0.x release: GOWDK v0.2
GOWDK v0.2 is an experimental 0.x compiler/runtime release.
Not production-ready. Public syntax, generated output, runtime packages, and
tooling contracts may change before a stable release.
Implemented
- Open-ended 0.x hardening checklist with per-version planning buckets.
- v0.2 release checklist for Public Truth and Release Trust work.
- Release note template requiring experimental, not-production-ready, known
gaps, checksum, and attestation sections. - README experimental status, project laws, and current support matrix.
- Getting started release-install path with Linux, macOS, Windows, checksum,
attestation, and VS Code.vsixverification notes. - Root
SECURITY.mdaligned with the deeper repository security baseline. - Public issue templates for compiler, generated output, runtime, docs,
examples, language, addon, and non-sensitive security hardening reports. - Release workflow support for version-specific release notes files.
v0.1.5GitHub release metadata corrected to pre-release with an
experimental/not-production-ready warning at the top of the release body.- Public hardening labels from
docs/engineering/release-plan.md. - Public backlog issues for current
PartialPRDs:
#1 through
#13. - Public backlog issues for selected
Plannedroadmap items:
#15 through
#35. - Public release-plan bucket and detailed backlog issues:
#36 through
https://github.com/cssbruno/GoWDK/issues/70. - Focused follow-up issues for optional dependencies, release trust, compiler
spine, diagnostics, Go interop, endpoint/security hardening, components,
VS Code, contracts, dev overlay, and the flagship example:
#71 through
#114. - Public
0.x Hardeningproject board:
https://github.com/users/cssbruno/projects/2.
Partial
gowdk doctoris referenced as planned install verification but is not
implemented yet.
Planned
- Automated release body validation for experimental warning,
not-production-ready warning, known gaps, checksum instructions, and
attestation instructions. - Broader release smoke tests for generated app HTTP behavior.
- Automated docs link checking and Markdown lint.
Intentionally Out Of Scope
- Production-readiness claims.
- Migration guides.
- Framework comparison docs as core positioning.
- Mandatory npm, Tailwind, Gin, Echo, Fiber, Redis, NATS, or WebSocket
dependencies. - New compiler syntax or runtime feature expansion.
Known Gaps
- v0.2 is primarily a trust/docs/release hygiene slice, not a compiler feature
release. - Generated output remains pre-1.0 and unstable unless a reference doc marks a
surface stable.
Breaking Or Unstable Generated Output
Generated output is pre-1.0. Treat generated Go, generated JavaScript,
manifests, build reports, route reports, and runtime package contracts as
unstable unless a reference doc explicitly marks a surface stable.
Required Release Verification
Run the full checklist before publishing:
docs/engineering/v0.2-release-checklist.md
Required local gates:
git diff --check
go test ./...
go run golang.org/x/vuln/cmd/govulncheck@latest ./...
go build ./cmd/gowdk
node --check editors/vscode/extension.js
node --check editors/vscode/extension-core.js
node --test editors/vscode/*.test.jsArtifact Verification
Download the CLI artifact for your platform and checksums.txt from the GitHub
release.
grep ' <artifact>$' checksums.txt | sha256sum -c -On macOS, use:
shasum -a 256 <artifact>Verify GitHub artifact attestations:
gh attestation verify <artifact> -R cssbruno/GOWDKVS Code Extension
Install the packaged .vsix manually when the release includes one:
code --install-extension gowdk-vscode-<version>.vsixTool Versions
- Go:
1.26.4 - Node.js for extension checks:
24