Build Linux aarch64 wheels by extending the build_wheels job in the
workflow to also run on an `ubuntu-22.04-arm` runner.
In order for this to work, the commit also extends the `install-go.sh`
helper architecture aware.
For GitHub first party actions (actions from the github.com/actions
organisation) we just use a major version tag. For actions from any
other source we pin to an exact commit SHA1 (and put the version in
a comment)
Use the GitHub setup-go action to install Go, as it is not in the
Mac OS runner images by default.
I tried but failed to get a Windows wheel build working, so that
remains disabled for now.
Bazel 7 is currently in maintenance and supported to the end of 2026.
The CI build should require an up-to-date lockfile so that we can try
to catch before merging if Bazel dep changes are made without the
corresponding lockfile change.
* chore: Update dependency versions
* Downgrade crypto to fix bazel CI
* Switch to Go 1.23.7 and update dependencies
Signed-off-by: Andrii Korotkov <andrii.korotkov@verkada.com>
- Checkout with submodules, otherwise the sdist won't include libjsonnet.h
- Install golang in the cibuildwheel build container.
- Skip musllinux build; it's not working for me.
- Skip Windows platform builds; they're not working for me.
It would be nice to get the other platforms working but I have already
spent hours on this and haven't succeeded yet. Previous go-jsonnet
releases on PyPI didn't have prebuilt wheel packages anyway, so it's
still strictly better to have some rather than none even if not all
platforms are covered.
This corresponds to a similar commit on the C++ jsonnet repo:
a02a615def
The is intended to make it easier for me to trigger running CI on
existing pull requests.
If it's not tested, then it doesn't work. Add a CI test that
executes `bazel build //...` and `bazel test //...`, in addition to
the non-bazel build system.
Motivation: make darwin_arm64 artifact available as part of the release
The *Installation instructions* already refers to Go v1.17 and above, and
the README.md states:
*We recommend always using the newest stable release of Go.*
Please note, that is not yet a working change set. It appears that a
go mod tidy
is needed to make the build step work.
