-
Notifications
You must be signed in to change notification settings - Fork 219
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
CompatHelper: bump compat for ADTypes to 1, (keep existing compat) #2200
CompatHelper: bump compat for ADTypes to 1, (keep existing compat) #2200
Conversation
b983949
to
af867d1
Compare
Probably need to bump in DPPL, etc. first, no? Tests will be using old version I believe |
Pull Request Test Coverage Report for Build 8839150395Details
💛 - Coveralls |
Yes, currently some dependencies don't support ADTypes 1.0. I started with tpapp/LogDensityProblemsAD.jl#28 |
…39-856-03977648508
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be good to go now
Seems some (test?) dependency holds it back: https://github.com/TuringLang/Turing.jl/actions/runs/8839150395/job/24271862153?pr=2200#step:6:79 |
Shite. It's AdvancedVI.jl... |
Double shite. I thought we were on AdvanceVI.jl 0.1..... 🤦 |
Attempt number 2: TuringLang/AdvancedVI.jl#56 |
Shite. Didn't mean to merge this 🤦 |
Once TuringLang/AdvancedVI.jl#56 goes through and is released, I'll make a new PR for this. Thought I was looking at another PR and saw all the green lights so hit merge.. |
This pull request changes the compat entry for the
ADTypes
package from0.2
to0.2, 1
.This keeps the compat entries for earlier versions.
Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass before you merge this pull request.