Skip to content

fix: dev-tagged subarr-subgen builds don't nag a backward update#233

Merged
coaxk merged 1 commit into
mainfrom
fix/subgen-dev-tag-no-update
Jun 13, 2026
Merged

fix: dev-tagged subarr-subgen builds don't nag a backward update#233
coaxk merged 1 commit into
mainfrom
fix/subgen-dev-tag-no-update

Conversation

@coaxk

@coaxk coaxk commented Jun 13, 2026

Copy link
Copy Markdown
Owner

Your soak box (and any locally-built subarr-subgen) bakes a dev-<sha> release tag via scripts/build.sh. The #224 update comparison ranked dev-5db497b against the latest release v2026.05.3-r8, found them different, and reported "update available" — pointing BACKWARD to r8 even though the dev build is the newer r9 candidate.

Fix: a dev- (or missing) tag is an unreleased, uncomparable version → resolve to None, the same "unknown current → show latest, never claim an update" bucket #224 established. Extracted to a _subgen_update_version helper with tests.

Released images (r9+) carry proper v2026.05.3-rN tags and compare correctly — unaffected. Verified live on :9923: the subarr-subgen update badge cleared (has_update False).

A local/soak image bakes a dev-<sha> release tag (scripts/build.sh) that
cannot be ranked against date-style release tags, so the #224 comparison
reported a difference and pointed the user BACKWARD to the latest
release. Treat a dev/missing tag as unknown (None) — same bucket as #224:
show the latest release, never claim an update. Extracted to a tested
_subgen_update_version helper.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coaxk coaxk merged commit 5242408 into main Jun 13, 2026
14 checks passed
@coaxk coaxk deleted the fix/subgen-dev-tag-no-update branch June 13, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant