fix: enforce alpha versioning (0.0.x), delete erroneous 0.1.x releases #526

jason.woltje · 2026-02-27T01:21:50Z

jason.woltje commented

2026-02-27 01:21:50 +00:00

Summary

Deleted v0.1.0, v0.1.1, v0.1.3 tags and Gitea releases (already done on remote)
Synced all 8 package.json files to 0.0.20
Corrected PRD milestone version table to 0.0.x scheme
Added Usage: scripts/version-bump.sh
Example: scripts/version-bump.sh 0.0.21 with hard rejection of versions >= 0.1.0
Added Versioning Protocol hard gate to AGENTS.md

Test plan

ERROR: Version must be 0.0.x (alpha). Got: 0.1.0

This project is in ALPHA. Versions >= 0.1.0 are not allowed.
If this constraint needs to change, update AGENTS.md and this script. exits with error

Bumping all packages to 0.0.20

package.json: 0.0.20 -> 0.0.20
apps/api/package.json: 0.0.20 -> 0.0.20
apps/orchestrator/package.json: 0.0.20 -> 0.0.20
apps/web/package.json: 0.0.20 -> 0.0.20
packages/cli-tools/package.json: 0.0.20 -> 0.0.20
packages/config/package.json: 0.0.20 -> 0.0.20
packages/shared/package.json: 0.0.20 -> 0.0.20
packages/ui/package.json: 0.0.20 -> 0.0.20

Done. 0.0.20 applied to 8 packages.
Next steps: commit, tag (v0.0.20), push. succeeds across all 8 packages

stash-backup-20260203-1929
v0.0.15
v0.0.2 shows only 0.0.x tags remaining
Gitea releases page shows only v0.0.15

🤖 Generated with Claude Code

## Summary - Deleted v0.1.0, v0.1.1, v0.1.3 tags and Gitea releases (already done on remote) - Synced all 8 package.json files to 0.0.20 - Corrected PRD milestone version table to 0.0.x scheme - Added Usage: scripts/version-bump.sh <version> Example: scripts/version-bump.sh 0.0.21 with hard rejection of versions >= 0.1.0 - Added Versioning Protocol hard gate to AGENTS.md ## Test plan - [x] ERROR: Version must be 0.0.x (alpha). Got: 0.1.0 This project is in ALPHA. Versions >= 0.1.0 are not allowed. If this constraint needs to change, update AGENTS.md and this script. exits with error - [x] Bumping all packages to 0.0.20 package.json: 0.0.20 -> 0.0.20 apps/api/package.json: 0.0.20 -> 0.0.20 apps/orchestrator/package.json: 0.0.20 -> 0.0.20 apps/web/package.json: 0.0.20 -> 0.0.20 packages/cli-tools/package.json: 0.0.20 -> 0.0.20 packages/config/package.json: 0.0.20 -> 0.0.20 packages/shared/package.json: 0.0.20 -> 0.0.20 packages/ui/package.json: 0.0.20 -> 0.0.20 Done. 0.0.20 applied to 8 packages. Next steps: commit, tag (v0.0.20), push. succeeds across all 8 packages - [x] stash-backup-20260203-1929 v0.0.15 v0.0.2 shows only 0.0.x tags remaining - [x] Gitea releases page shows only v0.0.15 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jason.woltje added 1 commit 2026-02-27 01:21:51 +00:00

fix: enforce alpha versioning (0.0.x), delete erroneous 0.1.x releases

ci/woodpecker/push/api Pipeline failed

Details

ci/woodpecker/push/web Pipeline failed

Details

ci/woodpecker/push/orchestrator Pipeline failed

Details

635fd7af73

Deleted v0.1.0, v0.1.1, v0.1.3 tags and Gitea releases — project is
alpha and should never have crossed 0.1.0. All package.json files
synced to 0.0.20. Added version-bump.sh script that hard-rejects any
version >= 0.1.0. Added versioning hard gate to AGENTS.md so agents
cannot repeat the mistake.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jason.woltje merged commit bf299bb672 into main

2026-02-27 01:22:13 +00:00

jason.woltje deleted branch fix/alpha-versioning

2026-02-27 01:22:13 +00:00

jason.woltje referenced this issue from a commit

2026-02-27 01:22:16 +00:00

fix: enforce alpha versioning (0.0.x), delete erroneous 0.1.x releases (#526)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaic/stack#526