e233a808c1
fix: exclude bazeliskrc from smoke test ( #654 )
2023-11-14 15:39:56 -08:00
541c014f7c
chore: update bcr maintainer list ( #644 )
2023-11-08 10:55:49 -08:00
fe2d31870c
chore: green up Windows CI ( #643 )
2023-11-07 14:01:45 -08:00
20f1ac39e0
refactor: rework toolchain registration for WORKSPACE and bzlmod users ( #597 )
2023-10-10 12:16:13 -07:00
4a4dafa6e8
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 15:57:29 -07:00
14d6c50fc5
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 09:01:51 -07:00
e30284f2fa
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.
2023-04-06 16:58:07 -07:00
e31867302e
chore: use coreutils hashsum ( #333 )
2023-03-10 20:37:57 +03:00
dead59b7b0
release: publish release artifact
...
GitHub's stability guarantee for the archive is iffy, and we want metrics on downloads.
See https://github.com/bazel-contrib/SIG-rules-authors/issues/11#issuecomment-1412241948
2023-02-01 10:43:45 -08:00
fc0ff4de2b
chore: update bcr homepage
2023-01-07 16:53:48 -08:00
f242667058
chore: declare bzlmod repository
...
This is needed to match what's in the upstream BCR now
2022-10-21 15:54:13 -07:00
c86f355dd0
ci: prepare bazel-lib for publish-to-bcr app
2022-09-10 12:30:53 -07:00
Derek Cormier