| name | gowdk-version-bump |
| description | Bump the GOWDK release version. Use when updating the CLI version, VS Code extension package version, install snippets, release docs, release notes, or validating a 0.x release metadata change. |
GOWDK Version Bump
Baselines
- Source of truth:
const version = "0.x.y" near the top of
internal/gowdkcmd/main.go (no v prefix). GitHub tags and install snippets
use v0.x.y. Current line: const version = "0.12.0".
editors/vscode/package.json must match the CLI constant exactly;
editors/vscode/scripts/sync-version.js reads the constant from
internal/gowdkcmd/main.go and writes/checks package.json. Never edit the
extension version by hand.- Pinned
v0.x.y install snippets live in README.md and
docs/getting-started.md (multiple snippets); release automation references
in docs/engineering/release.md.
CHANGELOG.md is the canonical change log and is managed by release-please
for release PRs. release.yml derives the visible GitHub release body from
the matching changelog section and fails when that section is missing.- Pull request titles must use Conventional Commits because squash merges feed
release-please changelog and release-note generation.
- Releases are tagged
v0.x.y and built by release.yml
(gh workflow run release.yml -f version=v0.x.y); smoke tests via
release-smoke.yml; VS Code Marketplace publish is a separate manual
workflow. Tagging is NOT part of this skill.
Core Workflow
- Confirm the target version (
0.x.y constant, v0.x.y everywhere else).
- Update
internal/gowdkcmd/main.go, then sync and check the extension:
node editors/vscode/scripts/sync-version.js
node editors/vscode/scripts/sync-version.js --check
- Update the pinned snippets and docs:
README.md,
docs/getting-started.md, and docs/engineering/release.md when cutting a
release. Let release-please update CHANGELOG.md for release PRs.
- Sweep for stragglers of the previous version and update only surfaces that
describe the current release (this includes the version mentions in this
skill file):
grep -rn "0\.3\.0\|v0\.3\.0" README.md docs/ cmd/ editors/vscode/package.json .agents/
Leave historical records (old CHANGELOG entries, dated release notes,
ADR dates) alone.
5. Verify:
go test ./cmd/gowdk -run Version
go run ./cmd/gowdk version --json
Guardrails
- Do not create tags or GitHub releases unless explicitly asked.
- Do not imply production readiness from a
0.x bump; release bodies must
keep the "Experimental 0.x release" framing even when GitHub release
metadata is not marked pre-release.
- Keep CLI and VS Code extension version changes intentional and documented.
