Skip to content

test: re-anchor the version-handshake test fixtures#136

Merged
Jammy2211 merged 1 commit into
mainfrom
docs/jax-install-and-version-sync
Jul 23, 2026
Merged

test: re-anchor the version-handshake test fixtures#136
Jammy2211 merged 1 commit into
mainfrom
docs/jax-install-and-version-sync

Conversation

@Jammy2211

@Jammy2211 Jammy2211 commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Re-anchors the check_version test 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 accidental run_number releases 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):

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.

Changed since the first revision

This PR originally also bumped autonerves/__init__.py to 2026.7.22.1. That has been dropped.

Releases are wheels+tags only (PyAutoBuild#118/#120): release.yml seds the version into the build tree and never commits back to any main. Main's __version__ is therefore expected to lag, and check_version is a compatibility floor, not an exact pin. Hand-bumping main re-establishes exactly the stamp-commit-back pattern #120 removed. Left at 2026.7.9.1.

151 passed.

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
Jammy2211 force-pushed the docs/jax-install-and-version-sync branch from 619bb23 to f875f74 Compare July 23, 2026 16:37
@Jammy2211 Jammy2211 changed the title chore: sync __version__ to 2026.7.22.1; re-anchor version test fixtures test: re-anchor the version-handshake test fixtures Jul 23, 2026
@Jammy2211
Jammy2211 merged commit 57406bd into main Jul 23, 2026
4 checks passed
@Jammy2211
Jammy2211 deleted the docs/jax-install-and-version-sync branch July 23, 2026 16:45
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