Adjust lower compats for compatibility with julia-1.11 #46
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.
Here are some changes to the lower package compats required to work on julia-1.11:
The type parameter in
AbstractTriangular
was removed in julia-1.11.As
AbstractTriangular
was explicitly called inFillArrays
until0.13.8
,the compat in the General registry was manually adjusted to disallow the use ofFillArrays
pre-0.13
with julia-1.11.==> I adjusted the lower compat of
FillArrays
to0.13.8
.BinaryProvider
is discontinued in julia-1.11.FFTW
directly depended onBinaryProvider
until1.1
.==> I adjusted the lower compat of
FFTW
to1.2
.SpecialFunctions
depended onBinaryProvider
until0.8
.In
RadiationDetectorDSP
,[email protected]
only allows for[email protected]
.==> I adjusted the lower compat of
DSP
to0.6.2
to also allow for[email protected]
.These changes should resolve the failing Downgrade tests.
The only question remaining: do we want an explicit version requirement for
SpecialFunctions ≥ 0.9
via weak dependencies here?