Allow LogExpFunctions v1#811
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Conversation
Widen the LogExpFunctions [compat] from "0.3" to "0.3, 1" so ForwardDiff can be installed alongside LogExpFunctions v1.x, while still supporting the existing 0.3 series. Bump the patch version to 1.3.4. The full test suite passes with LogExpFunctions v1.0.1 resolved. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisRackauckas
approved these changes
Jun 7, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #811 +/- ##
=======================================
Coverage 90.75% 90.75%
=======================================
Files 11 11
Lines 1071 1071
=======================================
Hits 972 972
Misses 99 99 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
|
There's already a pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
LogExpFunctions v1.0 has been released, but ForwardDiff's
[compat]entry still pinsLogExpFunctions = "0.3", which excludes the entire 1.x series. This PR widens the entry to"0.3, 1", keeping the existing 0.3 series so no current users are dropped while allowing installation alongside LogExpFunctions v1.x.DiffRules(ForwardDiff's dependency that actually consumes LogExpFunctions for its rule definitions) already allows v1 (LogExpFunctions = "0.3.2, 1"), so ForwardDiff's own cap is the remaining blocker for downstream packages that pull both the modern AD stack and LogExpFunctions 1.x.Changes
[compat] LogExpFunctions = "0.3"→"0.3, 1"1.3.3→1.3.4Testing
The full test suite passes with LogExpFunctions v1.0.1 resolved in the test environment (verified in both the test
Project.tomlandManifest.toml). On Julia 1.10.11:All test sets (Partials, Dual, Derivatives, Gradients, Jacobians, Hessians, Perturbation Confusion, Miscellaneous, Allocations, and the QA/JET checks) pass with no failures.
Motivation
This unblocks downstream packages that depend on both ForwardDiff and LogExpFunctions v1.x simultaneously, without forcing a constraint conflict in their environments.