bazel-lib
bazel-lib copied to clipboard
Common useful functions for writing BUILD files and Starlark macros/rules
@alexeagle this was mostly copy-pasta'ed from https://github.com/bazelbuild/rules_rust/issues/276#issuecomment-1320198911. Transitions are a new topic in Bazel for me. I'm not sure how to properly exercise or test the rule
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/bazel-contrib/bazel-lib). ## Config Migration Needed - [ ]...
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [io_bazel_rules_go](https://togithub.com/bazelbuild/rules_go) | http_archive | minor | `v0.35.0` -> `v0.37.0` | ---...
The last official jq release, and the one these rules are currently using, was released in 2018, it sounds like the project is still alive https://github.com/stedolan/jq/issues/2305 but changes aren't happening...
As far as I know, java_binary still can't be directly `bazel run` so that it starts in the working directory, and Java makes it nearly impossible to change the working...
Leaving a `TODO(2.0)` in the code for this
Useful for things like producing a package.json file that has the version field set from git tags.
I introduced a few todos in https://github.com/aspect-build/bazel-lib/commit/15ec78eb731eb679402f2d45b677ee02ab08735b - write_source_files - diff_test - Compile //:gazelle_bin We should figure out what's the issue with these and enable them on remote-exec.
Silently ignoring conflicts and not overwriting could be a source of tricky to find bugs. Both ignore and overwrite behaviours should be explicitly declared. fyi @devversion
`checkout` now needs to be explicit non-default workspaces no longer inherit root tasks by default