config: adopt version.minimum_library_version floor (2026.7.9.1)#32
Merged
Conversation
Phase 4 task 1 (PyAutoBuild#155). Move the compatibility floor to the canonical version.minimum_library_version key autoconf prefers over legacy workspace_version. Behavioural no-op: both resolve to 2026.7.9.1 (first post-redesign INSTALLABLE release; 2026.6.x-2026.7.6.649 are yanked). workspace_version kept until the version_skew rework reads it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Phase 4 task 1 of the build-chain campaign (PyAutoBuild#155), from
draft/feature/workspaces/minimum_library_version_adoption.md: adopt the canonicalversion.minimum_library_versioncompatibility floor in this workspace'sconfig/general.yaml, completing the migration off the legacyworkspace_versionkey (which releases stopped writing under PyAutoConf#119 / PyAutoBuild#121).This is a provable behavioural no-op:
autoconf.workspacealready resolves the floor asminimum_library_versionfirst, elseworkspace_version— and both are2026.7.9.1, so the effective floor is unchanged (verified by resolving it old-vs-new). The change just moves the value to the key the check actually prefers, so the legacy key andversion.txtcan later be retired (deferred to after the Heartversion_skewrework, which still readsworkspace_version— Phase 4 task 2).Floor value = 2026.7.9.1, chosen deliberately: it is the first release after the floor-model redesign (2026-07-08) and — the constraint the campaign's version-drift bug turned on — it is installable. Verified against PyPI: the 2026.6.x–2026.7.6.649 series is yanked; 2026.7.9.1 and 2026.7.15.1 are the only non-yanked recent releases. The floor names an installable version, and the co-located comment documents the bump-deliberately rule (moves only when scripts need new API, never per release).
workspace_versionis intentionally kept for now (removal is coordinated with theversion_skewrework that reads it).API Changes
None — workspace config only.
Test Plan
2026.7.9.1viaminimum_library_version(autoconf_yaml_version_value) — same value as the priorworkspace_versionfallback → no behaviour change.__version__is2026.7.9.1(≥ floor) →check_versionpasses.check_version).Generated by the PyAutoLabs agent workflow.