release: 1.4.0 — the findability fix, which is unreachable until it is tagged - #316
Merged
Merged
Conversation
…s tagged Bumps 1.3.0 -> 1.4.0. MINOR rather than PATCH by the same reasoning as 1.2.0: a previously-passing delivery can now stop. The guard refuses in four situations instead of two. That is a behaviour change a launcher must be told about, not a patch. Cut now rather than at convenience because the launcher installs from a git TAG (views-models tools/launcher/postprocessor.sh:57), not from PyPI and not from poetry.lock. Until this tag exists, the fix for today's unservable delivery is merged, reviewed, tested — and reachable by nothing. 1.2.0 sat unpinned for three weeks for exactly this reason. The changelog entry leads with the consequence for someone still on an older pin: a delivery can complete successfully and be unservable. Then what changed, then why taking it promptly is worth it — the deterministic-re-run case, where the dedup path that took one object takes all 110 and the documented remedy for a torn run is what triggers it. Recorded there as known-and-not-ours: pipeline-core's get_latest_file_id documents "newest by creation timestamp" over an unsorted result, which the SELECTION half of the guard has relied on since August. This release removes the equivalent assumption from the per-object half. The upstream half is filed there. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ANY1CCy9Xo7zjMY4XJ69v9
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
1 participant
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.
Bumps
1.3.0→1.4.0.Why now, not at convenience
The launcher installs from a git tag (
views-modelstools/launcher/postprocessor.sh:57) — not PyPI, not the lockfile. Until this tag exists, today's fix for an unservable delivery is merged, reviewed, tested, and reachable by nothing.1.2.0 sat unpinned for three weeks for exactly this reason.
Why MINOR
Same reasoning as 1.2.0: a previously-passing delivery can now stop. The guard refuses in four situations instead of two. No new exception types, but a real behaviour change a launcher must be told about.
What the entry leads with
The consequence for anyone still on an older pin — a delivery can complete successfully and be unservable — then what changed, then why promptness matters: pooling is deterministic and filenames embed the run id, so a re-run writes new names over identical bytes and the dedup path takes all 110 objects at once. Re-running is the documented remedy for a torn run.
Recorded as known-and-not-ours: pipeline-core's
get_latest_file_iddocuments "newest by creation timestamp" over an unsorted result, which the selection half has relied on since August. This release removes the equivalent assumption from the per-object half.Verification
Changelog and version only — no code. 526 passing on
developmentat this tree.🤖 Generated with Claude Code
https://claude.ai/code/session_01ANY1CCy9Xo7zjMY4XJ69v9