-
Notifications
You must be signed in to change notification settings - Fork 32
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
[Merged by Bors] - CompatHelper: bump compat for "ChainRulesCore" to "0.10" #255
[Merged by Bors] - CompatHelper: bump compat for "ChainRulesCore" to "0.10" #255
Conversation
118ca95
to
5fe18a1
Compare
Is anyone working to get this merged? Would be helpful to get it sorted, as it's currently blocking JuliaGaussianProcesses/AbstractGPs.jl#160 I believe. |
Unfortunately, this always takes a while since one has to update (and often fix) DistributionsAD and Bijectors. It took me a while to make all tests pass again on DistributionsAD again (some updates in SpecialFunctions and Zygote both broke and fixed different things) but I made a new release with updated ChainRules just a few hours ago. So now some of the fixes have to be applied to Bijectors as well and then one can push through this PR. |
Opened a PR to Bijectors: TuringLang/Bijectors.jl#182 |
bors try |
bors r+ |
This pull request changes the compat entry for the `ChainRulesCore` package from `0.9.7` to `0.9.7, 0.10`. 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. Co-authored-by: David Widmann <[email protected]>
This pull request changes the compat entry for the
ChainRulesCore
package from0.9.7
to0.9.7, 0.10
.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.