Skip to content

Support MODULE.bazel and REPO.bazel#503

Merged
meteorcloudy merged 1 commit intobazelbuild:masterfrom
crncnnr:new-workspace-boundaries
Nov 10, 2023
Merged

Support MODULE.bazel and REPO.bazel#503
meteorcloudy merged 1 commit intobazelbuild:masterfrom
crncnnr:new-workspace-boundaries

Conversation

@crncnnr
Copy link
Copy Markdown
Contributor

@crncnnr crncnnr commented Oct 2, 2023

As of Bazel 6.3.0, MODULE.bazel and REPO.bazel are also considered workspace boundaries. Bazelisk now searches for these in the same order Bazel does.

Fixes #502

As of Bazel 6.3.0, MODULE.bazel and REPO.bazel are also considered
workspace boundaries. Bazelisk now searches for these in the same order
Bazel does.
Copy link
Copy Markdown
Member

@meteorcloudy meteorcloudy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@meteorcloudy meteorcloudy merged commit b7f5c75 into bazelbuild:master Nov 10, 2023
@crncnnr crncnnr deleted the new-workspace-boundaries branch November 16, 2023 16:09
ti-chi-bot Bot referenced this pull request in PingCAP-QE/artifacts Nov 30, 2023
[![Mend Renovate logo
banner](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [bazelbuild/bazelisk](https://togithub.com/bazelbuild/bazelisk) |
minor | `v1.18.0` -> `v1.19.0` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>bazelbuild/bazelisk (bazelbuild/bazelisk)</summary>

###
[`v1.19.0`](https://togithub.com/bazelbuild/bazelisk/releases/tag/v1.19.0)

[Compare
Source](https://togithub.com/bazelbuild/bazelisk/compare/v1.18.0...v1.19.0)

Bazelisk v1.19.0 comes with two significant changes:

- `MODULE.bazel` and `REPO.bazel` files are now obeyed
([https://github.com/bazelbuild/bazelisk/pull/503](https://togithub.com/bazelbuild/bazelisk/pull/503))
- Users will see a progress bar during binary downloads
([https://github.com/bazelbuild/bazelisk/pull/511](https://togithub.com/bazelbuild/bazelisk/pull/511))

We’d like to thank our amazing contributors
[@&#8203;crncnnr](https://togithub.com/crncnnr) and
[@&#8203;katre](https://togithub.com/katre)!

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/PingCAP-QE/artifacts).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy41OS44IiwidXBkYXRlZEluVmVyIjoiMzcuNTkuOCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@Fergibson Fergibson mentioned this pull request Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MODULE.bazel and REPO.bazel are not supported

2 participants