deploylisted

# Deploy wipnote Run the full deployment pipeline for wipnote. ## Quick Deploy ```bash # Non-interactive (recommended for CI/automation) ./scripts/deploy-all.sh VERSION --no-confirm # Interactive (with confirmations) ./scripts/deploy-all.sh VERSION # Dry run (preview what would happen) ./scripts/deploy-all.sh VERSION --dry-run ``` ## What the Pipeline Does 1. **Pre-flight** — Verify clean git state, correct branch, current version 2. **Quality gates** — `go build ./...`, `go vet ./...`, `go test ./...` 3. **Version bump** — Update `plugin/.claude-plugin/plugin.json` 4. **Commit + tag** — `release: vX.Y.Z` commit, `vX.Y.Z` git tag 5. **Push** — Push commits and tags to origin/main 6. **GitHub Release** — Triggered automatically by `release-go.yml` workflow on `v*` tag ## Instructions for Claude When the user asks to deploy or release: 1. **Check for a version argument.** If not provided, read the current version from `plugin/.claude-plugin/plugin.json` and suggest the next patch/minor/major bump. 2. **Run the deploy script:** ```bash ./scripts/deploy-all.sh VERSION --no-confirm ``` 3. **If the script doesn't exist** (user is not in the wipnote dev repo), guide them through manual steps: ```bash # 1. Run quality gates go build ./... && go vet ./... && go test ./... # 2. Bump version in plugin.json # 3. Commit, tag, push git add plugin/.claude-plugin/plugin.json git commit -m "release: vVERSION" git tag vVERSION git push or