Bump compat lower bounds to exclude versions older than 6 months #297
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
This PR updates the minimum version requirements in Project.toml to exclude package versions released more than 6 months ago (before February 11, 2025).
Changes Made
Updated minimum versions:
0.1→0.1.42(latest within 6 months: v0.1.42 from Feb 25, 2025)7→7.19(latest within 6 months: v7.19.0 from May 12, 2025)0.8, 0.9→0.9.4(latest within 6 months: v0.9.5 from June 6, 2025, using v0.9.4 from March 28, 2025)0.5→0.5.16(latest within 6 months: v0.5.16 from April 17, 2025)Kept unchanged:
1.6(stdlib)1.6(stdlib)1(no releases within 6 months - latest was v1.4.3 from June 7, 2024)1.10(recent patches are within 6 months)Test Results
✅ All tests pass with the new compat bounds
Rationale
Maintaining compatibility with very old package versions can:
By setting a 6-month cutoff, we ensure reasonable compatibility while encouraging users to stay reasonably up-to-date.
🤖 Generated with Claude Code