Skip to content

Support DataInterpolations v10.1 in tests - #507

Merged
ChrisRackauckas merged 1 commit into
SciML:mainfrom
ChrisRackauckas-Claude:support-datainterpolations-v10
Sep 2, 2026
Merged

Support DataInterpolations v10.1 in tests#507
ChrisRackauckas merged 1 commit into
SciML:mainfrom
ChrisRackauckas-Claude:support-datainterpolations-v10

Conversation

@ChrisRackauckas-Claude

@ChrisRackauckas-Claude ChrisRackauckas-Claude commented Aug 31, 2026

Copy link
Copy Markdown
Member

Ignore this PR until it has been reviewed by @ChrisRackauckas.

What changed and why

Allow the root test environment to resolve DataInterpolations 10.1. The docs environment already gained v10.1 support in #506; this completes support for the executable ParametrizedInterpolation(BSplineInterpolation, ...) test path.

DataInterpolations v10 relabels the breaking APIs that have shipped since v9.2 and introduces no additional break. This package already uses the post-v9.2 B-spline constructor, so no source change is required: https://github.com/SciML/DataInterpolations.jl/releases/tag/v10.0.0

Verification

Before this change, forcing v10.1 in a clean worktree failed locally:

$ julia +release --project=. -e 'using Pkg; Pkg.add(PackageSpec(name="DataInterpolations", version="10.1.0"))'
ERROR: empty intersection between DataInterpolations@10.1.0 and project compatibility 9.2.0 - 9

After this change, the test environment resolved DataInterpolations v10.1.0:

$ GROUP=Core julia +release --project=. -e 'using Pkg; Pkg.test()'
Core/sources.jl | 64 pass | 1 pre-existing broken | 65 total
Testing ModelingToolkitStandardLibrary tests passed

$ GROUP=QA julia +release --project=. -e 'using Pkg; Pkg.test()'
QA/qa.jl | 20 pass | 20 total
Testing ModelingToolkitStandardLibrary tests passed

$ julia +release --project=.tmp/runic -m Runic --check .
$ typos Project.toml
$ git diff --check
# all exited 0

Not verified

julia +release --project=docs docs/make.jl resolved DataInterpolations 10.1.0 and completed doctests, then failed Documenter cross-reference validation. The same unresolved API references (HeatPort, OnePort, Flange, etc.) reproduce on clean upstream/main with DataInterpolations 9.5.0 and were exposed by Documenter 1.18.0's stricter @ref classification. This PR does not weaken or repair that separate baseline docs failure. It is tracked in #508.

The Julia pre-version matrix and downstream jobs were not run locally.

Reviewer note

The intentional judgment is to widen compat without changing source code: the only directly exercised breaking API is already written in its v9.2+/v10 form.

🤖 Generated with Codex CLI 0.151.0 (model: gpt-5; session: local Codex session ID 01a0588b-a3c5-7040-8363-097859b8f435)

Allow the package and its validation environments to resolve DataInterpolations 10.1.

Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>

Co-Authored-By: OpenAI Codex <noreply@openai.com>

Agent-Harness: Codex CLI 0.151.0

Agent-Model: gpt-5

Agent-Session: local Codex session ID 01a0588b-a3c5-7040-8363-097859b8f435

Copy link
Copy Markdown
Member Author

CI update:

Recorded by Codex CLI 0.151.0 (model: gpt-5; session: local Codex session ID 01a0588b-a3c5-7040-8363-097859b8f435).

@ChrisRackauckas
ChrisRackauckas marked this pull request as ready for review September 2, 2026 10:05
@ChrisRackauckas
ChrisRackauckas merged commit c873e68 into SciML:main Sep 2, 2026
9 of 11 checks passed
ChrisRackauckas added a commit that referenced this pull request Sep 7, 2026
- Drop stale [compat] majors older than one year (#505)
- build(deps): update DataInterpolations requirement from 6.4, 7, 8, 9.0 to 6.4, 7, 8, 9.0, 10.1 (#506)
- Support DataInterpolations v10.1 (#507)
- Fix Documenter binding references (#509)



Agent-Harness: Claude Code
Agent-Model: claude-opus-5[1m]
Claude-Session: https://claude.ai/code/session_014FEzNTLFutCmTEAZ3zBg5R

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants