Fix Julia deprecation warnings in CI scripts and tests #662
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
@latest
tag usage in GitHub Actions workflowsChanges Made
GitHub Actions Updates
julia-actions/julia-buildpkg@latest
with@v1.7.0
in Downstream.ymljulia-actions/julia-buildpkg
from@v1
to@v1.7.0
(latest) in Downgrade.ymljulia-actions/julia-runtest
from@v1
to@v1.11.2
(latest) in Downgrade.ymlJulia Language Fixes
src/generic_lufact.jl:72
LAPACK.chkfinite(A)
toLinearAlgebra.LAPACK.chkfinite(A)
for consistency with line 8alias_A
andalias_b
usage intest/resolve.jl:78
LinearAliasSpecifier
API to eliminate deprecation warningsTest Plan
--depwarn=yes
flag--depwarn=error
after fixing deprecated API usageVerification
The deprecation warning fix was tested with:
🤖 Generated with Claude Code