As part of the donation, we expect to move the repository to bazel-contrib/bazel-lib. This means that github-generated archives will remain stable, even as they redirect to existing releases. (The archive is sensitive to the repo name but not the org).
We also expect to rename the module from aspect_bazel_lib to bazel_lib to make it vendor-neutral. This poses a larger migration challenge. Users can be instructed how to use_repo, but we'll need to ensure that transitive deps work correctly. We also need to deal with toolchain_type symbols which are referenced by label.
Two changes may be considered by the maintainers following the move:
The aspect_bazel_lib module currently depends on bazel_skylib, as it was intended to augment the "Bazel standard library" rather than supplant it. Now that skylib is effectively "read-only" to the community, it may be desirable to port the remaining APIs from bazel_skylib so that it becomes a full replacement, and drop any dependency on bazel_skylib.
bazel-lib could also gain a "compatibility layer" such that users can keep load() statements which refer to @bazel_skylib but redirect the repository/module to bazel-lib, e.g with repo_name or --override_repository.
This issue follows the process at https://bazel-contrib.github.io/SIG-rules-authors/hosting-policy.html#adding-a-repo
As a consequence of https://github.com/orgs/bazelbuild/discussions/3, Aspect would like to donate https://github.com/aspect-build/bazel-lib to the Linux Foundation under the bazel-contrib GH org.
As part of the donation, we expect to move the repository to bazel-contrib/bazel-lib. This means that github-generated archives will remain stable, even as they redirect to existing releases. (The archive is sensitive to the repo name but not the org).
We also expect to rename the module from
aspect_bazel_lib
tobazel_lib
to make it vendor-neutral. This poses a larger migration challenge. Users can be instructed how touse_repo
, but we'll need to ensure that transitive deps work correctly. We also need to deal with toolchain_type symbols which are referenced by label.Two changes may be considered by the maintainers following the move:
load()
statements which refer to@bazel_skylib
but redirect the repository/module to bazel-lib, e.g withrepo_name
or--override_repository
.