bazel
/
bazel-lib
mirror of https://github.com/bazel-contrib/bazel-lib
2
0
Fork 0
Code Issues Releases Activity
bazel-lib/MODULE.bazel

83 lines
2.7 KiB
Plaintext
Raw Normal View History

test: introduce an e2e test asserting that bzlmod works
2022-04-27 04:07:17 +00:00
"aspect-build/bazel-lib"
module(
name = "aspect_bazel_lib",
chore: revert fancy release automation (#517) It doesn't work properly with Publish To BCR app parsing of the module file.
2023-09-06 23:18:53 +00:00
version = "0.0.0",
chore: drop Bazel 5 support for 2.0 (#585)
2023-10-05 21:18:42 +00:00
bazel_compatibility = [">=6.0.0"],
chore: run buildifier
2023-06-09 23:22:37 +00:00
compatibility_level = 1,
test: introduce an e2e test asserting that bzlmod works
2022-04-27 04:07:17 +00:00
)
chore: tidy in MODULE.bazel file (#846)
2024-05-14 07:17:27 +00:00
# Lower-bounds (minimum) versions for direct runtime dependencies
chore(deps): update dependency bazel_skylib to v1.5.0
2024-01-29 20:35:48 +00:00
bazel_dep(name = "bazel_skylib", version = "1.5.0")
chore: bump to Bazel 7.3.1 (#914)
2024-08-20 17:37:52 +00:00
bazel_dep(name = "platforms", version = "0.0.10")
chore: run buildifier
2023-06-09 23:22:37 +00:00
fix(stardoc): upgrade and stop skipping under bzlmod Newest stardoc has fixed it, and since bzlmod will select the lowest version in the dependencies, our bump here will take effect for users as well.
2023-05-17 15:04:42 +00:00
# 0.5.4 is the first version with bzlmod support
fix: update stardoc module to `0.7.1` Found when creating a new Bazel module repository via `bazel-contrib/rules-template`, updating the libs to their latest version, and testing in CI with Bazel `8.0.0rc1`. That generates an error such as: ``` ERROR: Traceback (most recent call last): File "${BAZEL_DIR}/external/stardoc+/stardoc/BUILD", line 72, column 16, in <toplevel> srcs = glob(["*.jar"]), Error in glob: glob pattern '*.jar' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob). ERROR: ${REPO}/docs/BUILD.bazel:5:23: Target '@@stardoc+//stardoc:templates/markdown_tables/module_extension.vm' contains an error and its package is in error and referenced by '//docs:rules' ``` This was fixed by the [`0.7.1` release of `bazelbuild/stardoc`](https://github.com/bazelbuild/stardoc/releases/tag/0.7.1).
2024-10-26 00:33:04 +00:00
bazel_dep(name = "stardoc", version = "0.7.1", repo_name = "io_bazel_stardoc")
test: introduce an e2e test asserting that bzlmod works
2022-04-27 04:07:17 +00:00
refactor: rework toolchain registration for WORKSPACE and bzlmod users (#597)
2023-10-10 19:16:13 +00:00
bazel_lib_toolchains = use_extension("@aspect_bazel_lib//lib:extensions.bzl", "toolchains")
bazel_lib_toolchains.copy_directory()
bazel_lib_toolchains.copy_to_directory()
bazel_lib_toolchains.jq()
bazel_lib_toolchains.yq()
bazel_lib_toolchains.coreutils()
bazel_lib_toolchains.tar()
feat: introduce zstd toolchain (#831)
2024-05-03 23:12:56 +00:00
bazel_lib_toolchains.zstd()
refactor: rework toolchain registration for WORKSPACE and bzlmod users (#597)
2023-10-10 19:16:13 +00:00
bazel_lib_toolchains.expand_template()
feat: implement bats test runner (#699)
2023-12-20 21:08:47 +00:00
bazel_lib_toolchains.bats()
refactor: make root workspace bzlmod only (#915)
2024-08-20 18:20:51 +00:00
use_repo(bazel_lib_toolchains, "bats_toolchains", "bsd_tar_toolchains", "copy_directory_toolchains", "copy_to_directory_toolchains", "coreutils_toolchains", "expand_template_toolchains", "jq", "jq_toolchains", "yq", "yq_toolchains", "zstd_toolchains")
feat: support stamp substituions (#435)
2023-05-16 23:14:50 +00:00
chore: update MODULE.bazel to use register_toolchains
2022-09-12 23:25:02 +00:00
register_toolchains(
fix: bzlmod toolchain registration for copy_directory & copy_to_directory (#336)
2023-01-17 03:37:36 +00:00
"@copy_directory_toolchains//:all",
"@copy_to_directory_toolchains//:all",
chore: update MODULE.bazel to use register_toolchains
2022-09-12 23:25:02 +00:00
"@jq_toolchains//:all",
"@yq_toolchains//:all",
feat: support stamp substituions (#435)
2023-05-16 23:14:50 +00:00
"@coreutils_toolchains//:all",
chore: run buildifier
2023-06-09 23:22:37 +00:00
"@expand_template_toolchains//:all",
feat: implement bats test runner (#699)
2023-12-20 21:08:47 +00:00
"@bats_toolchains//:all",
Use statically-linked bsdtar on all platforms (#804) * [tar] Switch to statically linked binaries * chore: don't use bsdtar for extract yet * chore: add dzbarsky integrity hashes * Upgrade to 3.7.2.bcr.2 (#806) * chore: replace URLs with aspect-build fork --------- Co-authored-by: David Zbarsky <dzbarsky@gmail.com>
2024-03-29 18:35:56 +00:00
"@bsd_tar_toolchains//:all",
fix: register @zstd_toolchains//:all (#832)
2024-05-04 15:15:20 +00:00
"@zstd_toolchains//:all",
chore: update MODULE.bazel to use register_toolchains
2022-09-12 23:25:02 +00:00
)
fix(stardoc): upgrade and stop skipping under bzlmod Newest stardoc has fixed it, and since bzlmod will select the lowest version in the dependencies, our bump here will take effect for users as well.
2023-05-17 15:04:42 +00:00
chore: tidy in MODULE.bazel file (#846)
2024-05-14 07:17:27 +00:00
####### Dev dependencies ########
refactor: rework toolchain registration for WORKSPACE and bzlmod users (#597)
2023-10-10 19:16:13 +00:00
refactor: consume tools from source if unstamped (#543)
2023-09-24 22:06:10 +00:00
# To allow /tools to be built from source
chore: rules_go is a non-dev dep at HEAD (#554) This ensures if you get a SHA of bazel-lib you build the tools/ from head
2023-09-27 16:01:51 +00:00
# NOTE: when publishing to BCR, we patch this to be dev_dependency, as we publish pre-built binaries
# along with our releases.
refactor: consume tools from source if unstamped (#543)
2023-09-24 22:06:10 +00:00
Fix bzlmod (#600) * fix: gazelle is not a devdep It's easy to see because we reference the symbol two lines below here * fix: gazelle must be a regular dep I found this mistake when trying to use bazel-lib in a downstream repo.
2023-10-08 22:57:29 +00:00
bazel_dep(
name = "gazelle",
chore: bump buildifier, go and gazelle deps (#845)
2024-05-14 06:30:19 +00:00
version = "0.36.0",
Fix bzlmod (#600) * fix: gazelle is not a devdep It's easy to see because we reference the symbol two lines below here * fix: gazelle must be a regular dep I found this mistake when trying to use bazel-lib in a downstream repo.
2023-10-08 22:57:29 +00:00
# In released versions: dev_dependency = True
)
bazel_dep(
name = "rules_go",
chore: bump buildifier, go and gazelle deps (#845)
2024-05-14 06:30:19 +00:00
version = "0.46.0",
Fix bzlmod (#600) * fix: gazelle is not a devdep It's easy to see because we reference the symbol two lines below here * fix: gazelle must be a regular dep I found this mistake when trying to use bazel-lib in a downstream repo.
2023-10-08 22:57:29 +00:00
repo_name = "io_bazel_rules_go",
# In released versions: dev_dependency = True
)
go_deps = use_extension(
"@gazelle//:extensions.bzl",
"go_deps",
# In released versions: dev_dependency = True
)
refactor: consume tools from source if unstamped (#543)
2023-09-24 22:06:10 +00:00
go_deps.from_file(go_mod = "//:go.mod")
use_repo(
go_deps,
"com_github_bmatcuk_doublestar_v4",
"org_golang_x_exp",
fix: add bzlmod use_repo of org_golang_x_sys (#896) Commit 3c121a9cd9c665f3aca903c473ec91dc8af68721 broke E2E tests with the following error: ``` (23:31:56) ERROR: no such package '@@[unknown repo 'org_golang_x_sys' requested from @@aspect_bazel_lib~]//unix': The repository '@@[unknown repo 'org_golang_x_sys' requested from @@aspect_bazel_lib~]' could not be resolved: No repository visible as '@org_golang_x_sys' from repository '@@aspect_bazel_lib~' ``` The build worked when operating within the `aspect_bazel_lib` repo itself, but not when importing it with Bzlmod. This is because the `org_golang_x_sys` repo is imported indirectly by `rules_go`'s `go_rules_dependencies` macro in the `WORKSPACE` file, which is still active under bzlmod because there is no `WORKSPACE.bzlmod` file to suppress it.
2024-08-09 00:57:03 +00:00
"org_golang_x_sys",
refactor: consume tools from source if unstamped (#543)
2023-09-24 22:06:10 +00:00
)
chore: tidy in MODULE.bazel file (#846)
2024-05-14 07:17:27 +00:00
host = use_extension("@aspect_bazel_lib//lib:extensions.bzl", "host", dev_dependency = True)
host.host()
use_repo(host, "aspect_bazel_lib_host")
fix(stardoc): upgrade and stop skipping under bzlmod Newest stardoc has fixed it, and since bzlmod will select the lowest version in the dependencies, our bump here will take effect for users as well.
2023-05-17 15:04:42 +00:00
fix: declare host_platform as non-dev dep (#945) Fix https://github.com/bazel-contrib/bazel-lib/issues/944
2024-09-24 01:43:45 +00:00
host_platform = use_extension("@platforms//host:extension.bzl", "host_platform")
chore: bump to Bazel 7.3.1 (#914)
2024-08-20 17:37:52 +00:00
use_repo(host_platform, "host_platform")
chore: cleanup before bazel-contrib handoff (#918) * chore: clenaup before bazel-contrib handoff * chore: apply lint fixes --------- Co-authored-by: Alex Eagle <alex@aspect.dev>
2024-09-02 16:32:38 +00:00
bazel_dep(name = "aspect_rules_lint", version = "1.0.0-rc10", dev_dependency = True)
chore(deps): update dependency bazel_skylib_gazelle_plugin to v1.5.0
2024-01-31 05:08:35 +00:00
bazel_dep(name = "bazel_skylib_gazelle_plugin", version = "1.5.0", dev_dependency = True)
chore: bump buildifier, go and gazelle deps (#845)
2024-05-14 06:30:19 +00:00
bazel_dep(name = "buildifier_prebuilt", version = "6.4.0", dev_dependency = True)
chore(deps): update dependency bazel_features to v0.2.0
2024-01-26 18:04:22 +00:00
bazel_dep(name = "bazel_features", version = "0.2.0", dev_dependency = True)