Skip to content

fix: separate workspace freshness from compatibility floor - #203

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/workspace-freshness-stamp
Oct 17, 2026
Merged

Jammy2211 merged 1 commit into
mainfrom
feature/workspace-freshness-stamp

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Healthy workspaces with deliberately old minimum library versions currently warn that the workspace is stale. Separate compatibility from freshness: continue enforcing minimum_library_version, but compare dates only against workspace_version (or legacy version.txt). Floor-only workspaces no longer warn solely because their compatibility floor is old.

Closes #202.

API Changes

No signature changes. check_version retains the minimum-version error and legacy compatibility precedence. Freshness warnings now identify the release stamp; malformed or missing stamps provide no freshness evidence. This benefits HowToFit and all workspace consumers without editing their floors.

Validation

Python 3.12: python -m pytest test_autonerves -q -n auto — 252 passed, 1 skipped. Regression coverage includes floor-only workspaces, matching releases, the 30-day boundary, stale stamps, YAML precedence, legacy version.txt, malformed stamps and compatibility errors. git diff --check passed.

Heart vitals: STALE, published reason release validation stale: source moved since rehearsal (PyAutoFit, PyAutoGalaxy, PyAutoLens). No release claim. Part of the authorized four-task HowToFit group; stop at PR review, no merge authorization.

@Jammy2211
Jammy2211 merged commit f116f70 into main Oct 17, 2026
3 checks passed
@Jammy2211
Jammy2211 deleted the feature/workspace-freshness-stamp branch October 17, 2026 17:53
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.

fix: separate workspace freshness from compatibility floor

1 participant