Skip to content

Allow Nx 1.0 - #54

Merged
mortont merged 1 commit into
elixir-nx:mainfrom
reidmorrison:allow-nx-1.0
Nov 9, 2026
Merged

mortont merged 1 commit into
elixir-nx:mainfrom
reidmorrison:allow-nx-1.0

Conversation

@reidmorrison

Copy link
Copy Markdown
Contributor

Widens the Nx requirement to ~> 0.6 or ~> 1.0, so Ortex can be installed next to Nx, EXLA and Bumblebee 1.0.

No code changes were needed. I ran the test suite against Nx 1.0.0 and all 117 tests pass (I temporarily dropped exla/torchx so the lock could move to 1.0.0). CI still runs Nx 0.6.2 from mix.lock, because the dev-only exla and torchx 0.6 keep it there. Happy to add an Nx 1.0 CI job if you'd like.

Widen the nx requirement from "~> 0.6" to "~> 0.6 or ~> 1.0" so Ortex
can be installed next to Nx, EXLA and Bumblebee 1.0.

No code changes are needed: the test suite passes unchanged on
Nx 1.0.0. The lock stays on Nx 0.6.2 because the dev-only exla and
torchx 0.6 dependencies hold it there.
@mortont
mortont merged commit 83d3af1 into elixir-nx:main Nov 9, 2026
2 checks passed
@mortont

mortont commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

Thanks!

@reidmorrison

Copy link
Copy Markdown
Contributor Author

Thanks for merging both of these so quickly!

Would you be open to cutting a 0.1.11 release? Hex still has 0.1.10, so projects on Nx 1.0 can't install Ortex from Hex yet, and the Elixir 1.19 inspect fix from #48 hasn't reached Hex users either. No rush at all, and if there's anything you'd like done before a release, I'm happy to help.

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