| commit | e30284f2fa781d33379d41ff3cc23eb436f6a38f | [log] [tgz] |
|---|---|---|
| author | Alex Eagle <alex@aspect.dev> | Thu Apr 06 16:56:17 2023 -0700 |
| committer | Alex Eagle <alex@aspect.dev> | Thu Apr 06 16:58:07 2023 -0700 |
| tree | f46eb15ae59a35471d47e9e29e80048a154de188 | |
| parent | be3e47f23964f024220e313bc9c385bb1aff0c67 [diff] |
chore: use config.yml to indicate releaser We want to cleanup our GitHub tokens, and this repo is different from all others by historical accident.
Base Starlark libraries and basic Bazel rules which are useful for constructing rulesets and BUILD files.
This module depends on bazel-skylib. In theory all these utilities could be upstreamed to bazel-skylib, but the declared scope of that project is narrow and it‘s very difficult to get anyone’s attention to review PRs there.
bazel-lib is just a part of what Aspect provides:
Installation instructions are included on each release: https://github.com/aspect-build/bazel-lib/releases
To use a commit rather than a release, you can point at any SHA of the repo.
For example to use commit abc123:
url = "https://github.com/aspect-build/bazel-lib/releases/download/v0.1.0/bazel-lib-v0.1.0.tar.gz" with a GitHub-provided source archive like url = "https://github.com/aspect-build/bazel-lib/archive/abc123.tar.gz"strip_prefix = "bazel-lib-0.1.0" with strip_prefix = "bazel-lib-abc123"sha256. The easiest way to do this is to comment out the line, then Bazel will print a message with the correct value.Note that GitHub source archives don't have a strong guarantee on the sha256 stability, see https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes