Repository navigation
Allow Nx 1.0 - #519
Merged
Merged
Allow Nx 1.0#519
Conversation
Kino only uses Nx.Tensor, Nx.type, Nx.shape, Nx.to_binary and Nx.Heatmap, all unchanged in 1.0. The lock moves to nx 1.0.0 so the tests run against it.
jonatanklosko
approved these changes
Sep 15, 2026
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
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.
Nx 1.0.0 is out and kino's
nx ~> 0.1keeps it out of the resolver, so anything depending on both kino and Nx 1.0 needs an override right now (Axon does, elixir-nx/axon#671). This widens it to~> 0.1 or ~> 1.0.Kino only uses
Nx.Tensor,Nx.type,Nx.shape,Nx.to_binaryandNx.Heatmap, all unchanged in 1.0. The lock moves to 1.0.0 so the tests run against it.