Holochain binaries for supported platforms
Looking after the binaries build is reasonably simple, until something breaks. The main things to look for are:
- The
versions.jsonthat lists a tag for each of Holochain, Kitsune2 and Lair. It is the maintainer's responsibility to check that the listed tags are compatible with each other. - The
holochaintag listed inversions.jsonis used to decide what Holochain release to publish binaries to. - The
build.yamlthat is a multipurpose build workflow. It is used to check PRs and, on every push tomainormain-0.6, builds and publishes binaries to theholochainrepository. - The
check.yamlworkflow that can be run against a Holochain release. It pulls all the binaries and tries to run them on the supported platforms. It prints a report at the end to let you know whether each one ran successfully.
This project is branched for each Holochain release. The main branch is for the upcoming release, the main-*
branches are for released versions. Doing a bump on any branch follows the same process:
- Update the tags in
versions.jsonto the desired versions. - Create a PR and check that the
build.yamlworkflow passes. - Merge the PR. The
build.yamlworkflow will run automatically on the resulting push tomain(ormain-0.6) and publish the binaries. - Optionally, run the
check.yamlworkflow against the new release to verify the binaries.
Binaries are published to the corresponding github release at holochain/holochain.