Skip to content

Allow buildozer target to be aliased (#23) #12

Allow buildozer target to be aliased (#23)

Allow buildozer target to be aliased (#23) #12

Triggered via push January 25, 2025 06:56
Status Success
Total duration 2m 38s
Artifacts

release.yml

on: push

Annotations

3 warnings
release / build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
release / build
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:28:1)
release / build
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:28:1)