split shim releases into per-package branches (#59)

This commit is contained in:
Adeeb Shihadeh
2026-03-14 14:42:00 -07:00
committed by GitHub
parent 14d916d054
commit 6bc1fe9a9a
2 changed files with 27 additions and 15 deletions

View File

@@ -42,9 +42,9 @@ contributions welcome for other platforms!
```python
dependencies = [
# use the releases branch for pre-built wheels
"capnproto @ git+https://github.com/commaai/dependencies.git@releases#subdirectory=capnproto",
"ffmpeg @ git+https://github.com/commaai/dependencies.git@releases#subdirectory=ffmpeg",
# use per-package release branches for pre-built wheels
"capnproto @ git+https://github.com/commaai/dependencies.git@release-capnproto#subdirectory=capnproto",
"ffmpeg @ git+https://github.com/commaai/dependencies.git@release-ffmpeg#subdirectory=ffmpeg",
# use the master branch to build the package on pip install
"capnproto @ git+https://github.com/commaai/dependencies.git@master#subdirectory=capnproto",
@@ -58,4 +58,4 @@ to add a new package:
* start a new top-level directory as a new package
* `./test.sh` tests the building of all packages
* on pushes to `master`, wheels are built for our target platforms and pushed to a GitHub release
* the `releases` branch contains shim packages that allow pointing to a git branch and always getting the appropriate wheel for your platform
* each `release-<package>` branch contains a single shim package, so old lockfiles keep resolving even as new packages are added