Per app beta and stable release tracking planned vs confirmed #14

Merged

Breadway merged 2 commits from feature/bug-23-releases into main 2026-10-12 09:53:11 +08:00

Conversation 0 Commits 2 Files changed 9 +666 -11

Breadway commented 2026-10-11 17:05:33 +08:00

Owner

Copy link

Part of BUG-EP1, implements breadboard issue BUG-23 (per app beta and stable release tracking). Stacked on the BUG-22 branch.

Clusters track planned vs confirmed beta and stable application releases: admin sets targets and confirms what shipped, beta never newer than stable, confirmations need a plan. The status endpoint exposes a releases object per channel. Versions reuse the dev/rc aware ordering.

Verified: cargo test (all suites green, 2 new tests), cargo clippy with -D warnings clean, cargo fmt clean.

Closes BUG-23

Part of BUG-EP1, implements breadboard issue BUG-23 (per app beta and stable release tracking). Stacked on the BUG-22 branch. Clusters track planned vs confirmed beta and stable application releases: admin sets targets and confirms what shipped, beta never newer than stable, confirmations need a plan. The status endpoint exposes a releases object per channel. Versions reuse the dev/rc aware ordering. Verified: cargo test (all suites green, 2 new tests), cargo clippy with -D warnings clean, cargo fmt clean. Closes BUG-23

Breadway added 1 commit 2026-10-11 17:05:34 +08:00

feat: per app beta and stable release tracking ... a37b69fc65

Track planned vs confirmed beta and stable application releases per
cluster: admin sets targets and confirms what actually shipped, with
beta never newer than stable and confirmations requiring a plan.
The public status endpoint exposes a releases object with planned,
shipped and shipped_in per channel. Release versions reuse the
dev/rc aware ordering.

Breadway added 1 commit 2026-10-11 20:50:47 +08:00

fix: validate release versions and ordering, show plans on fresh clusters ... f06bf20ca2

Address review on the release tracking slice:
- stage aware version ordering (dev < beta < rc < release), build
  metadata ignored, so 1.4-dev no longer sorts after 1.4-rc
- reject malformed versions and any confirmed beta/stable update that
  would invert the effective ordering, checked in one transaction
- expose planned releases on a single fresh cluster, not only duplicates

Breadway added 1 commit 2026-10-11 22:15:36 +08:00

Merge remote-tracking branch 'origin/feature/bug-22-progress' into feature/bug-23-releases ... b2e5f3c293

# Conflicts:
#	tests/admin.rs

Breadway added 1 commit 2026-10-11 23:46:34 +08:00

Merge remote-tracking branch 'origin/feature/bug-22-progress' into feature/bug-23-releases ... 2ce65646c1

# Conflicts:
#	README.md
#	src/db.rs
#	src/db/tests.rs

Breadway force-pushed feature/bug-23-releases from 2ce65646c1 to bc11f9b6bc 2026-10-12 09:21:57 +08:00 Compare

Breadway changed target branch from feature/bug-22-progress to main 2026-10-12 09:53:10 +08:00

Breadway merged commit aa0324ec99 into main 2026-10-12 09:53:11 +08:00

Breadway referenced this pull request from a commit 2026-10-12 09:53:11 +08:00

Per app beta and stable release tracking planned vs confirmed (#14)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Breadway/breadbug-server!14

No description provided.