Support Python 3.14 in bittensor 11.0.1 - #2974
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🛡️ AI Review — Skeptic (security review)VERDICT: SAFE BASELINE scrutiny — repository admin/nucleus-associated author; no Gittensor association found; The diff consistently expands SDK support to Python 3.14, updates matching documentation and tests, and regenerates lockfile metadata. The only resolved dependency version change is the declared development dependency bump for FindingsNo findings. ConclusionNo malicious behavior or security vulnerability was found in the supplied diff. 🔍 AI Review — Auditor (domain review)VERDICT: 👍 UNKNOWN Gittensor association; repository admin and established subtensor contributor, so standard correctness scrutiny applies. The Python 3.14 package metadata, lockfile, documentation, CLI smoke check, and dependency floor are consistent. The previously required stable-publication work from #2972 is now present in the base branch ( No runtime code is affected, and FindingsNo findings. Prior-comment reconciliation
ConclusionThe prior release blocker is resolved, and the PR is ready to merge into the V438 integration branch. 📜 Previous run (superseded)
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| [project] | ||
| name = "bittensor" | ||
| version = "11.0.0.dev0" | ||
| version = "11.0.1.dev0" |
There was a problem hiding this comment.
[HIGH] The 11.0.1 release still republishes an immutable core version
This branch bumps only the SDK version, while the current release workflow also builds and publishes bittensor-core at the already-released 0.1.0 version. PyPI rejects re-uploading an existing filename, so the publish job cannot deliver the promised bittensor 11.0.1. PR #2972 addresses this by bumping core to 0.1.1, updating the SDK constraint, and hardening stable publication. Make #2972 a prerequisite and rebase this PR onto it, or incorporate those changes here.
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👎 |
88968f6 to
aabb94d
Compare
| [project] | ||
| name = "bittensor" | ||
| version = "11.0.0.dev0" | ||
| version = "11.0.1.dev0" |
There was a problem hiding this comment.
[HIGH] The 11.0.1 release still republishes an immutable core version
The stable workflow builds and uploads both packages, but this branch still leaves sdk/bittensor-core-py/pyproject.toml at already-published version 0.1.0 and permits that version through bittensor-core>=0.1.0. PyPI versions are immutable, so publication cannot complete as described. PR #2972 supplies the required bittensor-core 0.1.1 bump, dependency floor, and retry-safe release pipeline; merge it first and rebase this PR.
aabb94d to
8f80ba1
Compare
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👎 |
| [project] | ||
| name = "bittensor" | ||
| version = "11.0.0.dev0" | ||
| version = "11.0.1.dev0" |
There was a problem hiding this comment.
[HIGH] The 11.0.1 release still republishes an immutable core version
The release remains coupled to bittensor-core 0.1.0, while the stable workflow builds and submits that already-published version alongside SDK 11.0.1. The corrective 0.1.1 versioning and publication changes are still isolated in #2972. Merge #2972 first and rebase this branch; otherwise this PR does not provide a self-contained, reliable path to the release promised in its description.
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👎 |
| [project] | ||
| name = "bittensor" | ||
| version = "11.0.0.dev0" | ||
| version = "11.0.1.dev0" |
There was a problem hiding this comment.
[HIGH] The 11.0.1 release still republishes an immutable core version
The base release workflow still stamps and uploads bittensor-core 0.1.0 alongside the SDK. Because that core version is already published and PyPI versions are immutable, publication of 11.0.1 cannot complete as described. PR #2972 bumps the core to 0.1.1 and makes stable publication retry-safe; merge it first and rebase this branch, retaining the Python 3.14 metadata changes.
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👎 |
8f80ba1 to
a38ca0d
Compare
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
2 participants
What changed
11.0.1with support declared for Python 3.10 through 3.14.import bittensorand thebtclientry point.Why
bittensor 11.0.0declaresRequires-Python <3.14. On Python 3.14, pip therefore selects the older compatible v10 SDK, which does not contain the unifiedbtclientry point. Because published PyPI metadata is immutable, support must ship in a new patch release.The SDK itself is compatible with Python 3.14; the exclusion was in package metadata rather than runtime behavior.
Impact
After
11.0.1is published, Python 3.14 users running the documented migration receive the unified v11 SDK and CLI. Python 3.10 through 3.13 remain supported, while unfinished Python 3.15 releases remain excluded.Validation
import bittensor,btcli --version, and package dependency compatibility.Stacked onto #2970 (
v438-release) so the package metadata and documentation can ship together.