-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Downstream updates tracker for v1.0 #44
Comments
Is it Christmas already? |
No, it's a Monday. That the list that needs work to update 😅 |
For most of those, the huge breaking change will be bumping Julia compat up to 1.10. If that is accepted, the rest is a bunch of renamings that I can try to contribute little by little |
Since I'm not a member of SciML, I can only create new PRs, not update those from CompatHelper though |
Most should already be bumped to v1.10. |
I'm trying to do one of the harder upgrades with SciML/NonlinearSolve.jl#426 Can someone make me a member of the NonlinearSolve repo, so that CI runs automatically on my commits? It's rather tedious to wait for maintainer approval. |
The CompatHelper PRs that were merged don't force ADTypes v1, since they still allow v0.2. I think the right approach is to force ADTypes v1, so that we can see whether it breaks stuff or not. That's what I did in SparseDiffTools and NonlinearSolve. However, a first step is to allow ADTypes non-exclusively everywhere so that downstream tests may run |
Most cases have very small usage of ADTypes. NonlinearSolve, SparseDiffTools, and BoundaryValueDiffEq are the three that require a deeper dive. |
Which dependents must we upgrade to use ADTypes v1.0?
Listed by topological order below:
I only tick the ones for which ADTypes v0.2 is no longer in the compat bound (see my comment below)
The text was updated successfully, but these errors were encountered: