Update nanobind-bazel version in Bazel document #766
Conversation
This file contains 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
|
Free-threading flag doc is still missing, will add that tomorrow. |
The code comment above the bzlmod usage was updated to reflect the change back to match nanobind SemVer exactly, starting from v2.2.0.
nicholasjng
force-pushed
the
bump-nanobind-bazel-docs
branch
from
160968d
to
7015ccd
Compare
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.
The code comment above the bzlmod usage was updated to reflect the change back to match nanobind SemVer exactly, starting from v2.2.0.
Hi Wenzel, this is the nanobind-bazel release for free-threading. I included a small cosmetic update of the Bazel doc, since I decided to make the change of following nanobind SemVer exactly with the newest release. More details can be found on the release page.