Releases: cssbruno/GoWDK
GOWDK v0.3.0
Experimental 0.x release: GOWDK v0.3
GOWDK v0.3 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
- M3 route, endpoint, and contract reportability for the current 0.x surface.
gowdk endpointsprints a versioned endpoint-only report for actions, APIs,
fragments, and routable command/query contract references.gowdk inspect tree --jsonprints a source-linked compiler node tree for
editor and tooling navigation.gowdk inspect endpoint-graph --jsonprints a source-linked endpoint dispatch
graph with pages, routes, endpoints, guards, handlers, bindings, and notes.gowdk routesexposes source spans, binding state, route params,
render/cache metadata, guards, planned handlers, and non-fatal route-mode
notes for the supported route and endpoint surface.gowdk buildwritesopenapi.jsonfor the routable web surface and
asyncapi.jsonfor contract integration-event metadata.gowdk check --jsondiagnostics can include related source locations, and
the language server reports those locations as related information.- A machine-checked
.gwdkconformance corpus pins accept/reject cases against
stable diagnostic codes. - A per-construct stability and deprecation table documents current language
support and is checked against the code registries. - The shared tokenizer/parser cutover records byte offsets for source positions
and keeps formatter indentation stable around braces inside strings,
comments, and template literals. - Guardless pages are default-denied in generated apps: omission produces a
warning, public access still requiresguard public, and pages with backend
endpoints still hard-error without an explicit guard. v0.3.0release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, release-doc current-version examples, and M3
release-note body.
Partial
- Route, endpoint, and contract reports are versioned for the current 0.x
surface, but broader exact source spans and future report fields may still be
added. - Generated OpenAPI and AsyncAPI reports cover the implemented routable web and
integration-event metadata slices, not every future API or contract shape. - Guard metadata is still generated access redundancy and does not replace
authorization in normal Go backend handlers and services.
Planned
- M4 Go interop: Go binding inspection, stubs, typed params, build/load
contracts, and package resolution. - M5 secure endpoint runtime: strict adapters, request limits, CSRF response
contract, panic boundaries, and tested failure paths. - M7 request-time SSR/hybrid hardening and later component/client-language
milestones remain separate work.
Intentionally Out Of Scope
- Production-readiness claims.
- Migration guides.
- Framework comparison docs as core positioning.
- Mandatory full-page SSR or full-page hydration.
- User-written JavaScript as the normal app contract.
- Mandatory Tailwind, npm, Gin, Echo, Fiber, Redis, NATS, or another optional
framework/tool dependency. - Replacing backend authorization with generated page guards.
Known Gaps
- v0.3 remains experimental and focused on reportability and language/compiler
hardening. - Generated output remains pre-1.0 and unstable unless a reference doc marks a
surface stable. - Secure runtime, SSR/hybrid, component/client, operations, and production
hardening milestones remain incomplete.
Breaking Or Unstable Generated Output
Generated output is pre-1.0. Treat generated Go, generated JavaScript,
manifests, build reports, route reports, endpoint reports, inspect reports, and
runtime package contracts as unstable unless a reference doc explicitly marks a
surface stable.
Required Release Verification
Run the full release checklist before publishing:
docs/engineering/release.mddocs/engineering/release-plan.md
Required local gates:
git diff --check
scripts/test-go-modules.sh
scripts/vulncheck-go-modules.sh
go build ./cmd/gowdk
node editors/vscode/scripts/sync-version.js --check
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-0.3.0.vsixTool Versions
- Go:
1.26.4 - Node.js for extension checks:
24
GOWDK v0.2.8
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
BuildConfig.Scriptsfor global script tags in generated build-time and
request-time HTML documents. UseType: "module"for ES module bundles.- Page and component
js "./file.js",js "./file.ts", and inlinejs {}
declarations for scoped browser module inclusion without loading those
modules on unrelated pages. - 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 shape, 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.
- Automated release-note validation for the release template, v0.2 draft notes,
and the selected release body in the release workflow. - Published artifact smoke workflow for Linux, macOS Intel, macOS ARM, and
Windows CLI artifacts. - Release policy guard script for no production-ready claim, no hidden mandatory
npm install in CI/release packaging, and visible pre-release metadata. gowdk version --jsonfor release workflow verification.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. v0.2.3release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, release-doc current-version examples, and
GitHub milestone policy.- Parser-style regular-expression cleanup across compiler, LSP, CSS/glob
rewriting, runtime form scanning, and generated action validation paths. - Optional framework/context bridge and nested optional adapter modules for
Echo, Fiber, Gin, Redis Streams, NATS, and WebSocket fanout. v0.2.5release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Explicit page access metadata: real page sources must declare
@guard publicfor intentionally public pages or protected guard IDs for
guarded pages. - Thin native RBAC guard IDs through
role:<name>andpermission:<name>,
backed by application-ownedruntime/auth.Providerimplementations. - Generated guarded apps fail Go compilation when required backing hooks are
missing:GOWDKGuardRegistryfor custom guards andGOWDKAuthProviderfor
native RBAC guards. v0.2.6release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Optional
@pageannotations with filename-derived page IDs, while keeping
explicit@routeand@guardmetadata required. gowdk initnow scaffolds the thinner route-first page shape and keeps
public pages explicit through@guard public.- Release packaging uploads
dist/*as a GitHub Actions workflow artifact and
verifies the selected tag release contains the expected download assets. v0.2.7release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.gowdk.Config.Envdeclares normal env vars and secrets separately, validates
empty names, duplicate names, secret-looking normal vars, and required names
that are unset or blank.- Generated embedded apps and backend-only apps repeat required env checks
before serving requests. gowdk inspect irprints the validated compiler IR for M2 debugging.gowdk addwires built-in addons intogowdk.config.go.- Batteries-included auth and database addons provide common auth/session,
password hashing, and SQLC-style database wiring helpers. - Runtime request boundaries now include a default per-request deadline, API
request-body caps, recovered panic logging, and secret redaction. gowdk doctorchecks the local Go/GOWDK toolchain, project config, source
discovery, language validation, route metadata, and relevant optional tools
without writing generated output.v0.2.8release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Layout identity now comes from the
.layout.gwdkfile name.@layoutinside
a layout is optional and declares the parent layout(s) the layout inherits
from instead of its own identity. - Self-referential and cyclic layout inheritance are compile errors
(layout_self_reference,cyclic_layout_reference), and an@layoutparent
that does not resolve reportsunknown_layout_id. - A layout must contain exactly one
<slot />placeholder; zero or multiple
slots hard-error at validation time (layout_slot_count).
Partial
- Generated app HTTP smoke coverage remains narrower than the full runtime
surface.
Planned
- 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. - Replacing backend authorization with generated page guards.
Known Gaps
- v0.2 remains experimental and includes both release-trust work and early
compiler/runtime feature slices. - Generated output remains pre-1.0 and unstable unless a reference doc marks a
surface stable. - Guard metadata is a generated access redundancy layer and does not replace
authorization in normal Go backend handlers and services. - Env/secret metadata is a startup and config-load redundancy layer. Cloud
platforms, containers, process managers, and secret managers still inject
values, and backend authorization remains application-owned.
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
scripts/test-go-modules.sh
scripts/vulncheck-go-modules.sh
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
GOWDK v0.2.7
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
BuildConfig.Scriptsfor global script tags in generated build-time and
request-time HTML documents. UseType: "module"for ES module bundles.- Page and component
js "./file.js",js "./file.ts", and inlinejs {}
declarations for scoped browser module inclusion without loading those
modules on unrelated pages. - 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 shape, 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.
- Automated release-note validation for the release template, v0.2 draft notes,
and the selected release body in the release workflow. - Published artifact smoke workflow for Linux, macOS Intel, macOS ARM, and
Windows CLI artifacts. - Release policy guard script for no production-ready claim, no hidden mandatory
npm install in CI/release packaging, and visible pre-release metadata. gowdk version --jsonfor release workflow verification.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. v0.2.3release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, release-doc current-version examples, and
GitHub milestone policy.- Parser-style regular-expression cleanup across compiler, LSP, CSS/glob
rewriting, runtime form scanning, and generated action validation paths. - Optional framework/context bridge and nested optional adapter modules for
Echo, Fiber, Gin, Redis Streams, NATS, and WebSocket fanout. v0.2.5release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Explicit page access metadata: real page sources must declare
@guard publicfor intentionally public pages or protected guard IDs for
guarded pages. - Thin native RBAC guard IDs through
role:<name>andpermission:<name>,
backed by application-ownedruntime/auth.Providerimplementations. - Generated guarded apps fail Go compilation when required backing hooks are
missing:GOWDKGuardRegistryfor custom guards andGOWDKAuthProviderfor
native RBAC guards. v0.2.6release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Optional
@pageannotations with filename-derived page IDs, while keeping
explicit@routeand@guardmetadata required. gowdk initnow scaffolds the thinner route-first page shape and keeps
public pages explicit through@guard public.- Release packaging uploads
dist/*as a GitHub Actions workflow artifact and
verifies the selected tag release contains the expected download assets. v0.2.7release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.gowdk.Config.Envdeclares normal env vars and secrets separately, validates
empty names, duplicate names, secret-looking normal vars, and required names
that are unset or blank.- Generated embedded apps and backend-only apps repeat required env checks
before serving requests. gowdk inspect irprints the validated compiler IR for M2 debugging.gowdk addwires built-in addons intogowdk.config.go.- Batteries-included auth and database addons provide common auth/session,
password hashing, and SQLC-style database wiring helpers. - Runtime request boundaries now include a default per-request deadline, API
request-body caps, recovered panic logging, and secret redaction.
Partial
gowdk doctoris referenced as planned install verification but is not
implemented yet.
Planned
- 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. - Replacing backend authorization with generated page guards.
Known Gaps
- v0.2 remains experimental and includes both release-trust work and early
compiler/runtime feature slices. - Generated output remains pre-1.0 and unstable unless a reference doc marks a
surface stable. - Guard metadata is a generated access redundancy layer and does not replace
authorization in normal Go backend handlers and services. - Env/secret metadata is a startup and config-load redundancy layer. Cloud
platforms, containers, process managers, and secret managers still inject
values, and backend authorization remains application-owned.
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
scripts/test-go-modules.sh
scripts/vulncheck-go-modules.sh
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
GOWDK v0.2.6
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
BuildConfig.Scriptsfor global script tags in generated build-time and
request-time HTML documents. UseType: "module"for ES module bundles.- Page and component
js "./file.js",js "./file.ts", and inlinejs {}
declarations for scoped browser module inclusion without loading those
modules on unrelated pages. - 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 shape, 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.
- Automated release-note validation for the release template, v0.2 draft notes,
and the selected release body in the release workflow. - Published artifact smoke workflow for Linux, macOS Intel, macOS ARM, and
Windows CLI artifacts. - Release policy guard script for no production-ready claim, no hidden mandatory
npm install in CI/release packaging, and draft/pre-release release metadata. gowdk version --jsonfor release workflow verification.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. v0.2.3release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, release-doc current-version examples, and
GitHub milestone policy.- Parser-style regular-expression cleanup across compiler, LSP, CSS/glob
rewriting, runtime form scanning, and generated action validation paths. - Optional framework/context bridge and nested optional adapter modules for
Echo, Fiber, Gin, Redis Streams, NATS, and WebSocket fanout. v0.2.5release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Explicit page access metadata: real page sources must declare
@guard publicfor intentionally public pages or protected guard IDs for
guarded pages. - Thin native RBAC guard IDs through
role:<name>andpermission:<name>,
backed by application-ownedruntime/auth.Providerimplementations. - Generated guarded apps fail Go compilation when required backing hooks are
missing:GOWDKGuardRegistryfor custom guards andGOWDKAuthProviderfor
native RBAC guards. v0.2.6release metadata: CLI/editor versions, optional module root-version
requirements, root changelog, and release-doc current-version examples.- Optional
@pageannotations with filename-derived page IDs, while keeping
explicit@routeand@guardmetadata required. gowdk initnow scaffolds the thinner route-first page shape and keeps
public pages explicit through@guard public.- Release packaging uploads
dist/*as a GitHub Actions workflow artifact and
verifies the selected tag release contains the expected download assets.
Partial
gowdk doctoris referenced as planned install verification but is not
implemented yet.
Planned
- 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. - Replacing backend authorization with generated page guards.
Known Gaps
- v0.2 remains experimental and includes both release-trust work and early
compiler/runtime feature slices. - Generated output remains pre-1.0 and unstable unless a reference doc marks a
surface stable. - Guard metadata is a generated access redundancy layer and does not replace
authorization in normal Go backend handlers and services.
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
scripts/test-go-modules.sh
scripts/vulncheck-go-modules.sh
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
v0.2.5
GOWDK v0.2.0
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
GOWDK v0.1.5
Experimental 0.x release
Not production-ready. Public syntax, generated output, runtime packages, and tooling contracts may change before a stable release.
GOWDK v0.1.5 is part of the experimental 0.x pre-release line. Treat generated Go, generated JavaScript, manifests, and runtime package contracts as unstable unless the documentation explicitly marks a surface stable.
Known gaps and hardening work are tracked in the repository docs, including docs/engineering/release-plan.md and docs/engineering/v0.2-release-checklist.md.
GOWDK v0.1.0
GOWDK v0.1.0 is the first public 0.x release line.
This is pre-release compiler/runtime scaffolding, not a production-readiness claim. Until the full feature set is complete, public releases advance by minor version only: v0.1.0, v0.2.0, v0.3.0, and so on.
Included artifacts:
- gowdk-linux-amd64
- gowdk-linux-arm64
- gowdk-darwin-amd64
- gowdk-darwin-arm64
- gowdk-windows-amd64.exe
- checksums.txt
- gowdk-vscode-0.1.3.vsix
Highlights:
- Source-build CLI version set to 0.1.0.
- Static output, generated app, binary, and WASM deploy documentation updated.
- Missing-work checklist restored.
- Obsolete .llm plan documents removed.
- CI and release gates passed for this tag.