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)
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>
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.
