-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TagBot's suggested compat bounds for stdlibs at odds with PSA recommendation #292
Comments
If we change the compat entry for Downloads to "1.6", Julia v1.6 throws an error in CI:
See https://github.com/JuliaVTK/ReadVTK.jl/actions/runs/6689378728/job/18172832287?pr=46#step:5:39 in https://github.com/JuliaVTK/ReadVTK.jl/pull/46/files |
This was referenced Oct 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958
Last night, TagBot has started suggesting compat bounds for several stdlibs in several respositories, e.g., PackageCompiler.jl or ReadVTK.jl. There, however, it seems like the suggested compat bound is always just
"1"
, even though the Julia compat is"1.6"
.This mismatch between TagBot and the PSA recommendation is at least weird for package maintainers who are not in the loop regarding the further development of upgradeable stdlibs: Should we just wait for TagBot to update everything to
"1"
? Or should we go ahead and manually set it to the Julia compat?And is this mismatch just due to a limitation of TagBot not being able to extract the Julia compat for use in stdlibs, or is it an actual bug?
Either way, it would be great to see some guidance on this in the TagBot README and/or the PSA.
cc @vchuravy
The text was updated successfully, but these errors were encountered: