test: re-anchor the version-handshake test fixtures#136
Merged
Conversation
The `check_version` fixtures were pinned to April 2026 values and the colab mock returned `2026.7.6.649` — one of the accidental run_number releases that was yanked from PyPI. Re-anchor them on current, installable values. These are arbitrary sentinels; nothing reads a real release. What matters is the deltas, not the absolute dates (`_STALENESS_WINDOW_DAYS = 30`): | Fixture | Old | New | Delta | |---|---|---|---| | base workspace version | 2026.4.13.6 | 2026.7.22.1 | anchor | | within-window library | 2026.4.20.1 | 2026.7.29.1 | +7d <= 30 -> silent | | beyond-window library | 2026.6.1.1 | 2026.9.9.1 | +49d > 30 -> warns | | colab mock version | 2026.7.6.649 | 2026.7.22.1 | off the yanked release | Unchanged deliberately: `2025.1.1.1` (the "much older" mismatch sentinel) and `2027.1.1.1` (far-future sentinel proving `minimum_library_version` is the floor). A blanket find-replace collapses these into the base value and breaks the mismatch/ordering tests — verified, it fails exactly 3 tests. `__version__` is deliberately NOT touched. Releases are wheels+tags only (PyAutoBuild#118/#120): `release.yml` seds the version into the build tree and never commits back to any main, so main's `__version__` is expected to lag and hand-bumping it re-establishes the pattern #120 removed. 151 passed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Jammy2211
force-pushed
the
docs/jax-install-and-version-sync
branch
from
July 23, 2026 16:37
619bb23 to
f875f74
Compare
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.
Re-anchors the
check_versiontest fixtures. Fixtures only —__version__is not touched.Why
The fixtures were pinned to April 2026 values, and the colab mock returned
2026.7.6.649— one of the accidentalrun_numberreleases that was yanked from PyPI. A test fixture should not name an uninstallable version.The deltas, not the dates
These are arbitrary sentinels; nothing reads a real release. What matters is the deltas (
_STALENESS_WINDOW_DAYS = 30):2026.4.13.62026.7.22.12026.4.20.12026.7.29.12026.6.1.12026.9.9.12026.7.6.6492026.7.22.1Unchanged deliberately:
2025.1.1.1(the "much older" mismatch sentinel) and2027.1.1.1(far-future sentinel provingminimum_library_versionis the floor). A blanket find-replace collapses these into the base value and breaks the mismatch/ordering tests — verified, it fails exactly 3 tests.Changed since the first revision
This PR originally also bumped
autonerves/__init__.pyto2026.7.22.1. That has been dropped.Releases are wheels+tags only (PyAutoBuild#118/#120):
release.ymlseds the version into the build tree and never commits back to any main. Main's__version__is therefore expected to lag, andcheck_versionis a compatibility floor, not an exact pin. Hand-bumping main re-establishes exactly the stamp-commit-back pattern #120 removed. Left at2026.7.9.1.151 passed.