Bump numba upper bound to <=0.66.0 (main) - #2273
Merged
Merged
Conversation
github-actions
Bot
added
maintenance
numba
dependencies
Install numba==<cap> in the test and benchmark jobs, reading the cap from pyproject.toml, so CI validates the exact version the bump-numba workflow pins. If conda-forge lacks that version the solve fails loudly instead of silently testing an older release.
ricardoV94
force-pushed
the
auto/bump-numba-main-0.66.0
branch
from
July 30, 2026 08:41
9e78b92 to
f0775ea
Compare
ricardoV94
approved these changes
Jul 30, 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
1 participant
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.
numba 0.66.0 is available on PyPI. This PR raises the upper bound in
pyproject.tomlto<=0.66.0so the normal Tests workflow validates the new release. Merge after CI passes.Note: GitHub suppresses workflow runs triggered by the default
GITHUB_TOKEN, so CI (Tests, mypy, etc.) will not start automatically on this PR. Close and reopen it (or push an empty commit) to trigger the checks.