Skip to content

v2.10.8 — first PyPI release

Latest
Latest

Choose a tag to compare

View all tags
@volgin volgin released this 29 May 08:10
· 1 commit to main since this release
v2.10.8
0cbe41c

Highlights

  • First PyPI release. boltz-community is now installable from PyPI: pip install boltz-community and uv add boltz-community both work without a git URL (#12).
  • Releases are now tag-driven via GitHub Actions + PyPI Trusted Publisher (OIDC). No long-lived API tokens stored anywhere; each publish is gated by a required-reviewer rule on the pypi GitHub environment.

Install

# from PyPI (new, recommended)
pip install boltz-community
pip install "boltz-community[cuda]"     # with NVIDIA CUDA kernels

# uv works the same way
uv add boltz-community

# bleeding-edge from main (still supported)
pip install "boltz-community @ git+https://github.com/Novel-Therapeutics/boltz-community.git"

Details

What changed

  • pyproject.toml metadata (6de6485): added description, explicit license = MIT, authors (Wohlwend / Corso / Passaro — upstream authors), maintainers (this fork), keywords, 10 standard classifiers, and a [project.urls] block with Homepage / Source / Issues / Changelog / Upstream. The fork relationship is now discoverable from the PyPI page itself.
  • Tag-driven release workflow (fe42db2): new .github/workflows/release.yml fires on v*.*.* tag pushes (and manual workflow_dispatch). Two jobs:
    • build — sdist + wheel via python -m build, validated with twine check, uploaded as a 7-day GitHub artifact.
    • publish — downloads the artifacts and publishes via pypa/gh-action-pypi-publish using PyPI Trusted Publisher. Requires id-token: write (OIDC) and runs inside the pypi GitHub environment so PyPI can verify the workflow identity.
  • Releasing section in README (fe42db2): documents the one-time PyPI Trusted Publisher binding, the GitHub environment setup, the per-release flow as a 7-step checklist, and recovery guidance for failed publishes.

Fork etiquette

Standard things this release also nails down explicitly on the published artifact:

  • LICENSE is preserved verbatim — upstream MIT copyright (Wohlwend, Corso, Passaro 2024) is unchanged.
  • PyPI Author field lists the upstream authors; Maintainer field lists this fork. Bug reports go to our issue tracker, not theirs.
  • ## Cite section in the README continues to point at the original Boltz-1, Boltz-2, and ColabFold papers.
  • [project.urls].Upstream points at jwohlwend/boltz so anyone landing on the PyPI page sees the relationship at a glance.

Commits since v2.10.7

  • 0cbe41c Release 2.10.8 — first PyPI publish
  • fe42db2 Add tag-driven PyPI release workflow + Releasing docs
  • 6de6485 Fill out PyPI metadata in pyproject.toml
Assets 2
Loading