v0.5.2 — Dependency updates and Python 3.15 support
GitHub releaseSource-backed
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
Update dependencies and add tested support for Python 3.15. · Refresh 19 locked dependencies, uv/uv_build to 0.13.5, and four pinned GitHub Actions. · Require certifi >=2026.10.23 for installed consumers as well as development and CI environments. · Add Python 3.15 to package… Show allShow less
- Update dependencies and add tested support for Python 3.15.
- Refresh 19 locked dependencies, uv/uv_build to 0.13.5, and four pinned GitHub Actions.
- Require certifi >=2026.10.23 for installed consumers as well as development and CI environments.
- Add Python 3.15 to package classifiers and the test and release verification matrices, alongside Python 3.13 and 3.14.
- Update PyCryptodome to 3.24.1, the latest compatible version while eth-hash 0.8.0 requires PyCryptodome <4. Validation: Python 3.13/3.14/3.15 test suites, mypy, offline web3 examples, workflow lint, byte-identical wheel/sdist…
Record ship:855f34a0… · HEY counts it as building; it does not judge the release’s quality.
Release, read from the team’s GitHub · no deployment linked
- What it names
- The team’s release names it: “v0.5.2 — Dependency updates and Python 3.15 support”.
- Stage
- A release is code the team published; HEY has not observed it deployed unless a link below says so.
- Reported by
- Read from the team’s GitHub. Independently recorded: a package version published from the same repository matches it (pypi many-abis@
0.5.2). - Release and deployment
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
- Activity
- No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
- When
- The source dates it 2026-10-25 06:01 UTC; HEY first knew on 2026-10-25.
- Not known
- HEY does not hold the commit the release was cut from.
- HEY has not observed a deployment of this change.
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Evidence: ship record
A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.