k8s(prod): promote v0.8.14 by digest - #368
Merged
Merged
Conversation
Prod has been on v0.8.12 throughout, so this is the first release carrying the #356 fractional-overlay fix. v0.8.13 was tagged but never promoted: it shipped the #364 binder error, and its promote PR (#362) was closed as superseded. Digest resolved via the GHCR anonymous-pull manifest HEAD, cross-checked two ways — the v0.8.14 tag and the 0f2fc25 git-sha tag return the same digest — and the method validated by resolving v0.8.12 to sha256:332d6df…, which matches the digest this commit replaces.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes prod v0.8.12 → v0.8.14. Replaces #362 (v0.8.13), closed as superseded.
Digest cross-checked two ways — the
v0.8.14tag and the0f2fc25…git-sha tag resolve to the same digest — and the method validated by resolvingv0.8.12, which returnssha256:332d6df…, exactly the digest this commit replaces.Why this matters
Prod has been on v0.8.12 the whole time, so it is still serving the pre-#357 unweighted overlay guidance — the silent-wrong-answer bug from #356 that a partner reported against the published 2025 Biodiversity Assessment. This is the first release that actually fixes it.
What ships
h3_cell_area, use publishedhex-weights, bound with the ecoregion land grid (#356)land_area_km2, not the removednland(#364)Validation
res-10 path — gated on dev, 3 trials × 2 models: 6/6. Zero occurrences of the pre-fix 28.8% form and zero of the 32.1% wrong-method-inside-tolerance form. Every trial carried the area term and applied the California mask.
res-8 path — verified by hand, because the tier cannot test it. This is the honest caveat: the regression tier has no res-8 question, which is exactly how #364 shipped through a green 6/6 gate. Direct check of the shipped recipe:
nlandcount-weightingCoverage gap filed as geo-agent-benchmark#21; do not read the 6/6 as covering the coarse path.
Baseline unchanged: Mojave 7,373,400 · GAP 1+2 26,471,500 · hardwood woodland 13.6% · California 26.08–26.1% · BioRank 21.18–21.2 · channelized 22.5%.
After merge
Coordination
Further edits to this guidance block are sequenced under #367, behind the gate-coverage work (geo-agent-benchmark#21, #16, #9). This should be the last patch to that section before a single design pass covering #363/#354/#355/#289/#353.