Alberto Cavalcante
Alberto Cavalcante
Updating bazelisk to use the latest Bazel release.
This is a proposal to add support for env expansion as `os.MkdirAll` will treat shell variables and `~` as literals. Fixes https://github.com/bazelbuild/bazelisk/issues/586
Currently if someone sets in `.bazeliskrc` the following home paths: ```txt BAZELISK_HOME=$HOME/.bazelisk ``` ```txt BAZELISK_HOME=~/.bazelisk ``` It will invoke `os.MkdirAll` with the raw string, therefore creating a `./'$HOME'` and `./'~'`...
Stopped using commit hash in favor of tag release at https://github.com/marketplace/actions/pypi-publish
### What is the current behavior? Today if I run `aspect init` it clones https://github.com/aspect-build/aspect-workflows-template: https://github.com/aspect-build/aspect-cli/blob/39875c856b24e185d93bcd0cbb1956245792767a/pkg/aspect/init/init.go#L76 and enters interactive mode. If a user do not proceed (hits `CTRL + C`)...
### What happened? When running `aspect init` at a directory that contains a dirty worktree, it fails with the following: ```sh $ aspect init {"level":"warn","time":"2024-07-03T03:22:20-03:00","message":"working tree is dirty, use --force...
### What happened? I still may need to re-reproduce and confirm my findings but I'm already sharing it anyway. I'll update this issue accordingly. The error I'm currently getting: **Standalone...
## TL;DR The canonical reference to `rules_antlr` is lost. The proposal is to transfer it to [bazel-contrib](https://github.com/bazel-contrib). Help wanted. ## Context I'm creating this issue as @marcohu hasn't been active...
I noticed that this project is dual-licensed under both the `MIT` and `Apache 2.0` licenses. Just curious, is there a specific reason for choosing to offer both licenses? Thanks!
Bazel 7.3.0 has been released. - https://github.com/bazelbuild/bazel/releases/tag/7.3.0