diff --git a/about/faq.mdx b/about/faq.mdx
index 03fb0c11..fa5a4d0c 100644
--- a/about/faq.mdx
+++ b/about/faq.mdx
@@ -155,7 +155,7 @@ For other IDEs, check out the [blog post](https://blog.bazel.build/2016/06/10/id
Bazel returns a non-zero exit code if the build or test invocation fails, and this should be enough for basic CI integration. Since Bazel does not need clean builds for correctness, the CI system should not be configured to clean before starting a build/test run.
-Further details on exit codes are in the [Scripts guide](/run/scripts#exit-codes).
+Further details on exit codes are in the [User Manual](/docs/user-manual).
## Can I use Bazel for my INSERT LANGUAGE HERE project?
diff --git a/configure/attributes.mdx b/configure/attributes.mdx
index 3b04298f..4f03c453 100644
--- a/configure/attributes.mdx
+++ b/configure/attributes.mdx
@@ -44,7 +44,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/configure/coverage.mdx b/configure/coverage.mdx
index 4a446218..1eacadfc 100644
--- a/configure/coverage.mdx
+++ b/configure/coverage.mdx
@@ -13,7 +13,9 @@ This page documents the general process for creating and viewing
coverage reports, and also features some language-specific notes for
languages whose configuration is well-known. It is best read by first
reading [the general section](#creating-a-coverage-report), and then
-reading about the requirements for a specific language.
+reading about the requirements for a specific language. Note also the
+[remote execution section](#remote-execution), which requires some
+additional considerations.
While a lot of customization is possible, this document focuses on
producing and consuming [`lcov`][lcov] reports, which is currently the
@@ -83,6 +85,32 @@ To view the result, simply open the `index.html` file produced in the
For further help and information around the `genhtml` tool, or the
`lcov` coverage format, see [the lcov project][lcov].
+## Remote execution {#remote-execution}
+
+Running with remote test execution currently has a few caveats:
+
+- The report combination action cannot yet run remotely. This is
+ because Bazel does not consider the coverage output files as part of
+ its graph (see [this issue][remote_report_issue]), and can therefore
+ not correctly treat them as inputs to the combination action. To
+ work around this, use `--strategy=CoverageReport=local`.
+ - Note: It may be necessary to specify something like
+ `--strategy=CoverageReport=local,remote` instead, if Bazel is set
+ up to try `local,remote`, due to how Bazel resolves strategies.
+- `--remote_download_minimal` and similar flags can also not be used
+ as a consequence of the former.
+- Bazel will currently fail to create coverage information if tests
+ have been cached previously. To work around this,
+ `--nocache_test_results` can be set specifically for coverage runs,
+ although this of course incurs a heavy cost in terms of test times.
+- `--experimental_split_coverage_postprocessing` and
+ `--experimental_fetch_all_coverage_outputs`
+ - Usually coverage is run as part of the test action, and so by
+ default, we don't get all coverage back as outputs of the remote
+ execution by default. These flags override the default and obtain
+ the coverage data. See [this issue][split_coverage_issue] for more
+ details.
+
## Language-specific configuration
### C++
@@ -116,3 +144,5 @@ for additional steps needed to enable coverage support in Python.
[lcov]: https://github.com/linux-test-project/lcov
[bazel_toolchains]: https://github.com/bazelbuild/bazel-toolchains
+[remote_report_issue]: https://github.com/bazelbuild/bazel/issues/4685
+[split_coverage_issue]: https://github.com/bazelbuild/bazel/issues/4685
diff --git a/contribute/codebase.mdx b/contribute/codebase.mdx
index 73f310e8..6c63f7e0 100644
--- a/contribute/codebase.mdx
+++ b/contribute/codebase.mdx
@@ -260,7 +260,7 @@ on Windows, where file names are case-insensitive.
Packages are independent of each other: changes to the `BUILD` file of a package
cannot cause other packages to change. The addition or removal of `BUILD` files
-_can_ change other packages, since recursive globs stop at package boundaries
+_can _change other packages, since recursive globs stop at package boundaries
and thus the presence of a `BUILD` file stops the recursion.
The evaluation of a `BUILD` file is called "package loading". It's implemented
@@ -305,7 +305,7 @@ Packages are composed of targets, which have the following types:
Bazel parlance, we call them _artifacts_ (discussed elsewhere). Not all
files created during the build are targets; it's common for an output of
Bazel not to have an associated label.
-2. **Rules:** these describe steps to derive their outputs from their inputs. They
+2. **Rules:** these describe steps to derive its outputs from its inputs. They
are generally associated with a programming language (such as `cc_library`,
`java_library` or `py_library`), but there are some language-agnostic ones
(such as `genrule` or `filegroup`)
@@ -353,7 +353,7 @@ of that type.
The evaluation framework underlying Bazel is called Skyframe. Its model is that
everything that needs to be built during a build is organized into a directed
-acyclic graph with edges pointing from any piece of data to its dependencies,
+acyclic graph with edges pointing from any pieces of data to its dependencies,
that is, other pieces of data that need to be known to construct it.
The nodes in the graph are called `SkyValue`s and their names are called
@@ -398,7 +398,7 @@ around this issue by:
limit the number of restarts.
2. Breaking up a `SkyValue` into separate pieces computed by different
`SkyFunction`s, so that they can be computed and cached independently. This
- should be done strategically, since it has the potential to increase memory
+ should be done strategically, since it has the potential to increases memory
usage.
3. Storing state between restarts, either using
`SkyFunction.Environment.getState()`, or keeping an ad hoc static cache
@@ -414,7 +414,7 @@ around this issue by:
[statemachine_example]: https://developers.google.com/devsite/reference/markdown/links#reference_links
-Fundamentally, Bazel needs these types of workarounds because hundreds of
+Fundamentally, Bazel need these types of workarounds because hundreds of
thousands of in-flight Skyframe nodes is common, and Java's support of
lightweight threads [does not outperform][virtual_threads] the
`StateMachine` implementation as of 2023.
@@ -526,9 +526,9 @@ affects test targets (we have plans to "trim" configurations so that this is
not the case, but it's not ready yet).
When a rule implementation needs part of the configuration, it needs to declare
-it in its definition using `RuleClass.Builder.requiresConfigurationFragments()`.
-This is both to avoid mistakes (such as Python rules using the Java fragment) and
-to facilitate configuration trimming so that if Python options change, C++
+it in its definition using `RuleClass.Builder.requiresConfigurationFragments()`
+. This is both to avoid mistakes (such as Python rules using the Java fragment) and
+to facilitate configuration trimming so that such as if Python options change, C++
targets don't need to be re-analyzed.
The configuration of a rule is not necessarily the same as that of its "parent"
@@ -559,7 +559,7 @@ Configuration transitions can also be implemented in Starlark (documentation
### Transitive info providers {#transitive-info-providers}
-Transitive info providers are a way (and the _only_ way) for configured targets
+Transitive info providers are a way (and the _only _way) for configured targets
to learn things about other configured targets that they depend on, and the only
way to tell things about themselves to other configured targets that depend on
them. The reason why "transitive" is in their name is that this is usually some
@@ -713,13 +713,13 @@ The concept of _toolchain_ comes from the fact that depending on what platforms
the build is running on and what platforms are targeted, one may need to use
different compilers; for example, a particular C++ toolchain may run on a
specific OS and be able to target some other OSes. Bazel must determine the C++
-compiler that is used based on the set execution and target platforms
+compiler that is used based on the set execution and target platform
(documentation for toolchains
[here](/extending/toolchains)).
In order to do this, toolchains are annotated with the set of execution and
target platform constraints they support. In order to do this, the definition of
-a toolchain is split into two parts:
+a toolchain are split into two parts:
1. A `toolchain()` rule that describes the set of execution and target
constraints a toolchain supports and tells what kind (such as C++ or Java) of
@@ -895,7 +895,7 @@ In order to get around this problem, we came up with the concept of a
`NestedSet`. It's a data structure that is composed of other `NestedSet`
instances and some members of its own, thereby forming a directed acyclic graph
of sets. They are immutable and their members can be iterated over. We define
-multiple iteration orders (`NestedSet.Order`): preorder, postorder, topological
+multiple iteration order (`NestedSet.Order`): preorder, postorder, topological
(a node always comes after its ancestors) and "don't care, but it should be the
same each time".
@@ -1062,7 +1062,7 @@ the set of inputs of an action come in two forms:
* An action may discover new inputs before its execution or decide that some
of its inputs are not actually necessary. The canonical example is C++,
where it's better to make an educated guess about what header files a C++
- file uses from its transitive closure so that we don't need to send every
+ file uses from its transitive closure so that we don't heed to send every
file to remote executors; therefore, we have an option not to register every
header file as an "input", but scan the source file for transitively
included headers and only mark those header files as inputs that are
@@ -1147,7 +1147,7 @@ More information about strategies (or action contexts!):
Bazel _can_ run many actions in parallel. The number of local actions that
_should_ be run in parallel differs from action to action: the more resources an
-action requires, the fewer instances should be running at the same time to avoid
+action requires, the less instances should be running at the same time to avoid
overloading the local machine.
This is implemented in the class `ResourceManager`: each action has to be
@@ -1289,7 +1289,7 @@ execution so that outputs of different tests are not interspersed.
This is implemented in the aptly-named `StreamedTestOutput` class and works by
polling changes to the `test.log` file of the test in question and dumping new
-bytes to the terminal where Bazel runs.
+bytes to the terminal where Bazel rules.
Results of the executed tests are available on the event bus by observing
various events (such as `TestAttempt`, `TestResult` or `TestingCompleteEvent`).
@@ -1377,7 +1377,7 @@ are provided:
* `bazel aquery` is used to investigate the action graph
Each of these is implemented by subclassing `AbstractBlazeQueryEnvironment`.
-Additional query functions can be done by subclassing `QueryFunction`
+Additional additional query functions can be done by subclassing `QueryFunction`
. In order to allow streaming query results, instead of collecting them to some
data structure, a `query2.engine.Callback` is passed to `QueryFunction`, which
calls it for results it wants to return.
@@ -1387,7 +1387,7 @@ classes, XML, protobuf and so on. These are implemented as subclasses of
`OutputFormatter`.
A subtle requirement of some query output formats (proto, definitely) is that
-Bazel needs to emit _all_ the information that package loading provides so that
+Bazel needs to emit _all _the information that package loading provides so that
one can diff the output and determine whether a particular target has changed.
As a consequence, attribute values need to be serializable, which is why there
are only so few attribute types without any attributes having complex Starlark
@@ -1523,7 +1523,7 @@ starting `@guava//` and expect that to mean different versions of it.
Therefore, Bazel allows one to re-map external repository labels so that the
string `@guava//` can refer to one Guava repository (such as `@guava1//`) in the
-repository of one binary and another Guava repository (such as `@guava2//`) in the
+repository of one binary and another Guava repository (such as `@guava2//`) the
repository of the other.
Alternatively, this can also be used to **join** diamonds. If a repository
@@ -1591,7 +1591,7 @@ to replay information to the UI caused by various kinds of cached processing,
for example, the warnings emitted by a cached configured target.
Some `EventHandler`s also allow posting events that eventually find their way to
-the event bus (regular `Event`s do _not_ appear there). These are
+the event bus (regular `Event`s do _not _appear there). These are
implementations of `ExtendedEventHandler` and their main use is to replay cached
`EventBus` events. These `EventBus` events all implement `Postable`, but not
everything that is posted to `EventBus` necessarily implements this interface;
@@ -1616,11 +1616,11 @@ Bazel is fast. Bazel is also slow, because builds tend to grow until just the
edge of what's bearable. For this reason, Bazel includes a profiler which can be
used to profile builds and Bazel itself. It's implemented in a class that's
aptly named `Profiler`. It's turned on by default, although it records only
-abridged data so that its overhead is tolerable; the command line
+abridged data so that its overhead is tolerable; The command line
`--record_full_profiler_data` makes it record everything it can.
It emits a profile in the Chrome profiler format; it's best viewed in Chrome.
-Its data model is that of task stacks: one can start tasks and end tasks and
+It's data model is that of task stacks: one can start tasks and end tasks and
they are supposed to be neatly nested within each other. Each Java thread gets
its own task stack. **TODO:** How does this work with actions and
continuation-passing style?
diff --git a/contribute/docs.mdx b/contribute/docs.mdx
index 55f8f1bb..cc240cc4 100644
--- a/contribute/docs.mdx
+++ b/contribute/docs.mdx
@@ -2,19 +2,42 @@
title: 'Contribute to Bazel documentation'
---
-Thank you for contributing to Bazel's documentation!
-## How docs work
-Bazel documentation lives in two repositories:
+Thank you for contributing to Bazel's documentation! There are a few ways to
+help create better docs for our community.
-- [`bazelbuild/bazel`](https://github.com/bazelbuild/bazel) — all doc content in the `docs/` folder. This is where you make changes.
-- [`bazel-contrib/bazel-docs`](https://github.com/bazel-contrib/bazel-docs) — the hosting and navigation layer (Mintlify config, sidebar, PR previews).
+## Documentation types
-Content changes always go to `bazelbuild/bazel`. Navigation changes go to `bazel-contrib/bazel-docs`.
+This site includes a few types of content.
-## Contributing
+ - *Narrative documentation*, which is written by technical writers and
+ engineers. Most of this site is narrative documentation that covers
+ conceptual and task-based guides.
+ - *Reference documentation*, which is generated documentation from code comments.
+ You can't make changes to the reference doc pages directly, but instead need
+ to change their source.
-- **Make a change or add a page** — see [Docs contribution workflow](/contribute/docs-contribution-workflow) for step-by-step instructions, from a quick typo fix to adding a new page.
-- **Update the sidebar navigation** — see [Update the docs navigation](/contribute/docs-navigation) for instructions on adding your new page to the left-hand nav in `bazel-contrib/bazel-docs`.
+## Documentation infrastructure
+Bazel documentation is served from Google and the source files are mirrored in
+Bazel's GitHub repository. You can make changes to the source files in GitHub.
+If approved, you can merge the changes and a Bazel maintainer will update the
+website source to publish your updates.
+
+
+## Small changes
+
+You can approach small changes, such as fixing errors or typos, in a couple of
+ways.
+
+ - **Pull request**. You can create a pull request in GitHub with the
+ [web-based editor](https://docs.github.com/repositories/working-with-files/managing-files/editing-files) or on a branch.
+ - **Bug**. You can file a bug with details and suggested changes and the Bazel
+ documentation owners will make the update.
+
+## Large changes
+
+If you want to make substantial changes to existing documentation or propose
+new documentation, you can either create a pull request or start with a Google
+doc and contact the Bazel Owners to collaborate.
diff --git a/contribute/search.mdx b/contribute/search.mdx
index 0875dde0..7bbea560 100644
--- a/contribute/search.mdx
+++ b/contribute/search.mdx
@@ -210,64 +210,64 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/contribute/statemachine-guide.mdx b/contribute/statemachine-guide.mdx
index 832c7549..4db66dfa 100644
--- a/contribute/statemachine-guide.mdx
+++ b/contribute/statemachine-guide.mdx
@@ -781,7 +781,7 @@ There's a couple of examples of error handling already in [`Tasks.lookUp` callba
callbacks as values. Such callbacks often have exclusive-or semantics, with
exactly one of a value or error being passed.
-The next section describes a subtle, but important interaction with Skyframe
+The next section describes a a subtle, but important interaction with Skyframe
error handling.
#### Error bubbling (--nokeep\_going) {#error-bubbling}
diff --git a/docs/android-ndk.mdx b/docs/android-ndk.mdx
index ff57bbae..abd76409 100644
--- a/docs/android-ndk.mdx
+++ b/docs/android-ndk.mdx
@@ -308,7 +308,7 @@ bazel build //my/cc/jni:target \
--platforms=//my/platforms:x86_64
```
-This approach affects the entire build tree.
+With this approach, the entire build tree is affected.
Note: All of the targets on the command line must be compatible with
building for Android when specifying these flags, which may make it difficult to
diff --git a/docs/configurable-attributes.mdx b/docs/configurable-attributes.mdx
index f906c15f..8048f3a6 100644
--- a/docs/configurable-attributes.mdx
+++ b/docs/configurable-attributes.mdx
@@ -44,7 +44,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/docs/sandboxing.mdx b/docs/sandboxing.mdx
index 24781323..aaadcd79 100644
--- a/docs/sandboxing.mdx
+++ b/docs/sandboxing.mdx
@@ -54,12 +54,7 @@ You can choose which kind of sandboxing to use, if any, with the
strategy makes Bazel pick one of the sandbox implementations listed below,
preferring an OS-specific sandbox to the less hermetic generic one.
[Persistent workers](/remote/persistent) run in a generic sandbox if you pass
-the `--worker_sandboxing` flag. In addition to the plain boolean form, the flag
-can be scoped to a specific worker-key mnemonic with
-`--worker_sandboxing==` (for example
-`--worker_sandboxing --worker_sandboxing=Javac=no` to sandbox all singleplex
-workers except `Javac`; a later plain boolean value applies to all mnemonics
-again).
+the `--worker_sandboxing` flag.
The `local` (a.k.a. `standalone`) strategy does not do any kind of sandboxing.
It simply executes the action's command line with the working directory set to
diff --git a/docs/user-manual.mdx b/docs/user-manual.mdx
index a4773339..7b02ecf3 100644
--- a/docs/user-manual.mdx
+++ b/docs/user-manual.mdx
@@ -1603,10 +1603,10 @@ be formatted to stay within 80 characters when possible.
#### `--test_tmpdir=path` {#test-tmpdir}
-Specifies temporary directory for tests. Each test will be executed in a
-separate subdirectory inside this directory. The directory will be cleaned at
-the beginning of each `bazel test` command.
-By default, Bazel will place this directory under the Bazel output base directory.
+Specifies temporary directory for tests executed locally. Each test will be
+executed in a separate subdirectory inside this directory. The directory will
+be cleaned at the beginning of the each `bazel test` command.
+By default, bazel will place this directory under Bazel output base directory.
Note: This is a directory for running tests, not storing test results
(those are always stored under the `bazel-out` directory).
diff --git a/extending/rules.mdx b/extending/rules.mdx
index 1b2e050b..976d46ac 100644
--- a/extending/rules.mdx
+++ b/extending/rules.mdx
@@ -820,7 +820,7 @@ Tools that are executed as part of the build (such as compilers or code generato
should be built for an exec configuration. In this case, specify `cfg = "exec"` in
the attribute.
-Otherwise, executables that are used at runtime (e.g. as part of a test) should
+Otherwise, executables that are used at runtime (such as as part of a test) should
be built for the target configuration. In this case, specify `cfg = "target"` in
the attribute.
diff --git a/external/migration_tool.mdx b/external/migration_tool.mdx
index d6a36590..cf59c153 100644
--- a/external/migration_tool.mdx
+++ b/external/migration_tool.mdx
@@ -70,7 +70,7 @@ Before you begin:
Once the prerequisites are met, run the following commands to use the migration
tool:
-
+
# Clone the Bazel Central Registry repository
git clone https://github.com/bazelbuild/bazel-central-registry.git
cd bazel-central-registry
@@ -127,7 +127,7 @@ To see the migration script in action, consider the following scenario when
Python, Maven and Go dependencies are declared in `WORKSPACE` file.
-
+
Click here to see `WORKSPACE` file
@@ -267,7 +267,7 @@ Moreover, to demonstrate usage of module extension, custom macro is invoked from
`WORKSPACE` and it is defined in `my_custom_macro.bzl`.
-
+
Click here to see `my_custom_macro.bzl` file
@@ -304,27 +304,27 @@ The first step is to follow [How to Use the Migration Tool](#migration-tool-how-
Then, running `migrate2bzlmod -t=//...` outputs:
-
+
bazel 7.6.1
Generating ./resolved_deps.py file - It might take a while...
- RESOLVED:rules_java has been introduced as a Bazel module.
- RESOLVED:bazel_gazelle has been introduced as a Bazel module.
- RESOLVED:io_bazel_rules_go has been introduced as a Bazel module.
- RESOLVED:rules_python has been introduced as a Bazel module.
- IMPORTANT: 3.11 is used as a default python version. If you need a different version, please change it manually and then rerun the migration tool.
- RESOLVED:my_python_deps has been introduced as python extension.
- RESOLVED:org_golang_x_net has been introduced as go extension.
- RESOLVED:rules_jvm_external has been introduced as a Bazel module.
- RESOLVED:org.antlr has been introduced as maven extension.
- RESOLVED:rules_shell has been introduced as a Bazel module.
+ RESOLVED:rules_java has been introduced as a Bazel module.
+ RESOLVED:bazel_gazelle has been introduced as a Bazel module.
+ RESOLVED:io_bazel_rules_go has been introduced as a Bazel module.
+ RESOLVED:rules_python has been introduced as a Bazel module.
+ IMPORTANT: 3.11 is used as a default python version. If you need a different version, please change it manually and then rerun the migration tool.
+ RESOLVED:my_python_deps has been introduced as python extension.
+ RESOLVED:org_golang_x_net has been introduced as go extension.
+ RESOLVED:rules_jvm_external has been introduced as a Bazel module.
+ RESOLVED:org.antlr has been introduced as maven extension.
+ RESOLVED:rules_shell has been introduced as a Bazel module.
Congratulations! All external repositories needed for building //... are available with Bzlmod!
- IMPORTANT: Fix potential build time issues by running the following command:
- bazel build --enable_bzlmod --noenable_workspace //...
+ IMPORTANT: Fix potential build time issues by running the following command:
+ bazel build --enable_bzlmod --noenable_workspace //...
- IMPORTANT:For details about the migration process, check `migration_info.md` file.
+ IMPORTANT:For details about the migration process, check `migration_info.md` file.
which gives the following important information:
@@ -346,10 +346,10 @@ which gives the following important information:
This section illustrates the migration of code from the `WORKSPACE` file to
`MODULE.bazel`.
-
-
+
## Tips with debugging {#migration-tool-tips}
@@ -641,7 +641,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
declared in the `WORKSPACE` file, which is particularly useful for the
debugging. You can see it as:
-
+
> Click here to see where and how the repo was declared in the WORKSPACE
file
@@ -650,7 +650,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
earlier [Migration Example](#migration-tool-example), that would look as:
1. Bazel module Dependency - `Migration of rules_python`
-
+
Found perfect name match in BCR: rules_python
Found partially name matches in BCR: rules_python_gazelle_plugin
@@ -663,7 +663,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
added.
2. Python extension - `Migration of my_python_deps`
-
+
pip.parse(
hub_name = "my_python_deps",
requirements_lock = "//:requirements_lock.txt",
@@ -674,7 +674,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
3. Maven extension - `Migration of org.antlr (px_deps):`
-
+
maven.artifact(
name = "px_deps",
group = "org.antlr",
@@ -685,7 +685,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
4. Go extension - `Migration of org_golang_x_net`
-
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/install/compile-source.mdx b/install/compile-source.mdx
index 480c6522..9479e0cb 100644
--- a/install/compile-source.mdx
+++ b/install/compile-source.mdx
@@ -189,7 +189,7 @@ You can also build Bazel from scratch, without using an existing Bazel binary.
2. Unpack the distribution archive somewhere on disk.
You should verify the signature made by Bazel's
- [release key](https://releases.bazel.build/bazel-release.pub.gpg) 3D5919B448457EE0.
+ [release key](https://bazel.build/bazel-release.pub.gpg) 3D5919B448457EE0.
### Step 2a: Bootstrap Bazel on Ubuntu Linux, macOS, and other Unix-like systems {#bootstrap-unix-overview}
@@ -203,7 +203,7 @@ For instructions for Windows, see [Bootstrap Bazel on Windows](#bootstrap-window
* **C++ build toolchain**
-* **JDK.** Version 25 is required.
+* **JDK.** Version 21 is required.
* **Python**. Version 3 is required.
@@ -211,7 +211,7 @@ For example on Ubuntu Linux you can install these requirements using the
following command:
```sh
-sudo apt-get install build-essential openjdk-25-jdk python3 zip unzip
+sudo apt-get install build-essential openjdk-21-jdk python3 zip unzip
```
#### 2.2. Bootstrap Bazel on Unix {#bootstrap-unix}
@@ -249,7 +249,7 @@ For instructions for Unix-like systems, see
* **The Visual C++ compiler.** Install the Visual C++ compiler either as part
of Visual Studio 2015 or newer, or by installing the latest [Build Tools for Visual Studio 2017](https://aka.ms/BuildTools).
-* **JDK.** Version 25 is required.
+* **JDK.** Version 21 is required.
* **Python**. Versions 2 and 3 are supported, installing one of them is
enough. You need the Windows-native version (downloadable from
@@ -278,14 +278,14 @@ For instructions for Unix-like systems, see
export BAZEL_VS="C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools"
export BAZEL_SH="$(cygpath -m $(realpath $(which bash)))"
export PATH="/c/python27:$PATH"
- export JAVA_HOME="C:/Program Files/Java/jdk-25"
+ export JAVA_HOME="C:/Program Files/Java/jdk-21"
or (using BAZEL\_VC):
export BAZEL_VC="C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC"
export BAZEL_SH="$(cygpath -m $(realpath $(which bash)))"
export PATH="/c/python27:$PATH"
- export JAVA_HOME="C:/Program Files/Java/jdk-25"
+ export JAVA_HOME="C:/Program Files/Java/jdk-21"
3. `cd` to the directory where you unpacked the distribution archive.
diff --git a/install/ubuntu.mdx b/install/ubuntu.mdx
index 7ea98ce5..c1e4e32e 100644
--- a/install/ubuntu.mdx
+++ b/install/ubuntu.mdx
@@ -43,7 +43,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/migrate/xcode.mdx b/migrate/xcode.mdx
index 9c366877..5f6a05a2 100644
--- a/migrate/xcode.mdx
+++ b/migrate/xcode.mdx
@@ -115,7 +115,7 @@ In the target, specify the following at the minimum:
binary.
* `provisioning_profile` - provisioning profile from your Apple Developer
- account (if building for an iOS device).
+ account (if building for an iOS device device).
* `families` (iOS only) - whether to build the application for iPhone, iPad,
or both.
diff --git a/query/cquery.mdx b/query/cquery.mdx
index 86c2d5ff..f7195d40 100644
--- a/query/cquery.mdx
+++ b/query/cquery.mdx
@@ -546,7 +546,7 @@ that is, it configures its tools in the [exec configuration](https://bazel.build
You can see the lingering effects of that transition below.
```
-$ cat > foo/BUILD <<<EOF
+$ cat > foo/BUILD <<
+
diff --git a/remote/output-directories.mdx b/remote/output-directories.mdx
index f55e438a..36710825 100644
--- a/remote/output-directories.mdx
+++ b/remote/output-directories.mdx
@@ -34,7 +34,7 @@ The solution that's currently implemented:
and on Windows it defaults to `%HOME%` if set, else `%USERPROFILE%`
if set, else the result of calling `SHGetKnownFolderPath()` with the
`FOLDERID_Profile` flag set. If the environment variable `$XDG_CACHE_HOME`
- is set on Linux, macOS, or Windows, the value `${XDG_CACHE_HOME}/bazel` will
+ is set on either Linux or macOS, the value `${XDG_CACHE_HOME}/bazel` will
override the default. If the environment variable `$TEST_TMPDIR` is set,
as in a test of Bazel itself, then that value overrides any defaults.
* Note that Bazel 8.x and earlier on macOS used `/private/var/tmp` as _outputRoot_,
diff --git a/remote/persistent.mdx b/remote/persistent.mdx
index 83186635..c0e7f1da 100644
--- a/remote/persistent.mdx
+++ b/remote/persistent.mdx
@@ -129,13 +129,7 @@ Passing the
[`--worker_sandboxing`](/reference/command-line-reference#flag--worker_sandboxing)
flag makes each worker request use a separate sandbox directory for all its
inputs. Setting up the [sandbox](/docs/sandboxing) takes some extra time,
-especially on macOS, but gives a better correctness guarantee. In addition to
-the plain boolean form, the flag may be scoped to a worker-key mnemonic as
-`--worker_sandboxing==`, allowing sandboxing to be enabled or
-disabled per mnemonic (for example
-`--worker_sandboxing --worker_sandboxing=Javac=no`). Later values override
-earlier ones for the mnemonics they affect, so a later plain
-`--worker_sandboxing` re-enables sandboxing for all mnemonics.
+especially on macOS, but gives a better correctness guarantee.
The
[`--worker_quit_after_build`](/reference/command-line-reference#flag--worker_quit_after_build)
@@ -243,8 +237,7 @@ might be helpful.
Using the `worker` strategy by default does not run the action in a
[sandbox](/docs/sandboxing), similar to the `local` strategy. You can set the
`--worker_sandboxing` flag to run all workers inside sandboxes, making sure each
-execution of the tool only sees the input files it's supposed to have, or scope
-it per mnemonic with `--worker_sandboxing==`. The tool
+execution of the tool only sees the input files it's supposed to have. The tool
may still leak information between requests internally, for instance through a
cache. Using `dynamic` strategy
[requires workers to be sandboxed](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/exec/SpawnStrategyRegistry.java).
diff --git a/remote/sandbox.mdx b/remote/sandbox.mdx
index 26e9b89b..de66ba6c 100644
--- a/remote/sandbox.mdx
+++ b/remote/sandbox.mdx
@@ -95,7 +95,7 @@ machine and is a reliable way to confirm whether your build will succeed when
executed remotely.
However, with this method, locally installed tools, binaries, and data may leak
-into your build, especially if it uses [configure-style WORKSPACE rules](/remote/rules#manage-workspace-rules).
+into into your build, especially if it uses [configure-style WORKSPACE rules](/remote/rules#manage-workspace-rules).
Such leaks will cause problems with remote execution; to detect them, [troubleshoot in a Docker container](#troubleshooting-docker-container)
in addition to troubleshooting natively.
diff --git a/rules/language.mdx b/rules/language.mdx
index 5e5d1069..a29111d8 100644
--- a/rules/language.mdx
+++ b/rules/language.mdx
@@ -55,7 +55,7 @@ Starlark in Bazel at HEAD is incrementally adding support for type annotations
with a syntax inspired by [PEP 484](https://peps.python.org/pep-0484/).
- Starlark type annotations are under active development. The progress is
- tracked on [issue#27370](https://github.com/bazelbuild/bazel/issues/27370).
+ tracked on [issue#22935](https://github.com/bazelbuild/bazel/issues/22935).
- The specification is incrementally extended: [starlark-with-types/spec.md](https://github.com/bazelbuild/starlark/blob/starlark-with-types/spec.md)
- Initial proposal: [SEP-001 Bootstrapping Starlark types](https://docs.google.com/document/d/1Sid7EAbBd_w_T7D94Li_f_bK3zMTztFbzIMvcpzo1wY/edit?tab=t.0#heading=h.5mcn15i0e1ch)
@@ -155,6 +155,7 @@ The following Python features are not supported:
* `class` (see [`struct`](/rules/lib/builtins/struct#struct) function).
* `import` (see [`load`](/extending/concepts#loading-an-extension) statement).
* `while`, `yield`.
+* float and set types.
* generators and generator expressions.
* `is` (use `==` instead).
* `try`, `raise`, `except`, `finally` (see [`fail`](/rules/lib/globals#fail) for fatal errors).
diff --git a/rules/rules-tutorial.mdx b/rules/rules-tutorial.mdx
index 8246f6b7..8510a81c 100644
--- a/rules/rules-tutorial.mdx
+++ b/rules/rules-tutorial.mdx
@@ -147,7 +147,7 @@ bin2
```
Whenever you declare a file, you have to tell Bazel how to generate it by
-creating an [action](/extending/rules#actions). Use [`ctx.actions.write`](/rules/lib/builtins/actions#write),
+creating an action. Use [`ctx.actions.write`](/rules/lib/builtins/actions#write),
to create a file with the given content.
```python
diff --git a/rules/testing.mdx b/rules/testing.mdx
index 499fa929..4642c9ea 100644
--- a/rules/testing.mdx
+++ b/rules/testing.mdx
@@ -159,7 +159,7 @@ would be named `testFoo`.
Then:
-* the macro which generates the test and target under test should be
+* the macro which generates the test and target under test should should be
named `_test_foo` (`_test_provider_contents`)
* its test rule type should be named `foo_test` (`provider_contents_test`)
diff --git a/run/scripts.mdx b/run/scripts.mdx
index 3a34e385..fcf0ef85 100644
--- a/run/scripts.mdx
+++ b/run/scripts.mdx
@@ -55,7 +55,7 @@ Bazel execution can result in following exit codes:
- `32` - External Environment Failure not on this machine.
- `33` - Bazel ran out of memory and crashed. You need to modify your command line.
-- `34` - Remote execution, remote cache, or Build Event Service error.
+- `34` - Reserved for Google-internal use.
- `35` - Reserved for Google-internal use.
- `36` - Local Environmental Issue, suspected permanent.
- `37` - Unhandled Exception / Internal Bazel Error.
@@ -64,7 +64,6 @@ Bazel execution can result in following exit codes:
- `41-44` - Reserved for Google-internal use.
- `45` - Persistent error publishing results to the Build Event Service.
- `47` - Reserved for Google-internal use.
-- `48` - External dependency error.
- `49` - Reserved for Google-internal use.
**Return codes for commands `bazel build`, `bazel test`:**
diff --git a/upstream b/upstream
index 3e93ad81..0faabafe 160000
--- a/upstream
+++ b/upstream
@@ -1 +1 @@
-Subproject commit 3e93ad81d20c0b2fb86bc04c8da3cde6f6a7cd80
+Subproject commit 0faabafe580979db81bda7b89985b68bb8965e2b
diff --git a/versions/7.6.1/configure/attributes.mdx b/versions/7.6.1/configure/attributes.mdx
index 6a37aacf..faa32464 100644
--- a/versions/7.6.1/configure/attributes.mdx
+++ b/versions/7.6.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/7.6.1/contribute/search.mdx b/versions/7.6.1/contribute/search.mdx
index 33ee794f..89e394c0 100644
--- a/versions/7.6.1/contribute/search.mdx
+++ b/versions/7.6.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/7.6.1/docs/configurable-attributes.mdx b/versions/7.6.1/docs/configurable-attributes.mdx
index 4a8a569e..f24dc320 100644
--- a/versions/7.6.1/docs/configurable-attributes.mdx
+++ b/versions/7.6.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/7.6.1/install/ubuntu.mdx b/versions/7.6.1/install/ubuntu.mdx
index 30355941..51556f91 100644
--- a/versions/7.6.1/install/ubuntu.mdx
+++ b/versions/7.6.1/install/ubuntu.mdx
@@ -40,7 +40,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/bazel-archive-keyring.gpg] https://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel.list
```
diff --git a/versions/7.7.1/configure/attributes.mdx b/versions/7.7.1/configure/attributes.mdx
index 8af6445a..57198598 100644
--- a/versions/7.7.1/configure/attributes.mdx
+++ b/versions/7.7.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/7.7.1/contribute/search.mdx b/versions/7.7.1/contribute/search.mdx
index 33ee794f..89e394c0 100644
--- a/versions/7.7.1/contribute/search.mdx
+++ b/versions/7.7.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/7.7.1/docs/configurable-attributes.mdx b/versions/7.7.1/docs/configurable-attributes.mdx
index 2cfddcc7..585578aa 100644
--- a/versions/7.7.1/docs/configurable-attributes.mdx
+++ b/versions/7.7.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/7.7.1/install/ubuntu.mdx b/versions/7.7.1/install/ubuntu.mdx
index 5fac25b4..d4bb33fd 100644
--- a/versions/7.7.1/install/ubuntu.mdx
+++ b/versions/7.7.1/install/ubuntu.mdx
@@ -40,7 +40,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/bazel-archive-keyring.gpg] https://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel.list
```
diff --git a/versions/8.0.1/configure/attributes.mdx b/versions/8.0.1/configure/attributes.mdx
index 2b3fa5b8..0e15e5fa 100644
--- a/versions/8.0.1/configure/attributes.mdx
+++ b/versions/8.0.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.0.1/contribute/search.mdx b/versions/8.0.1/contribute/search.mdx
index 50dc4164..9a721b88 100644
--- a/versions/8.0.1/contribute/search.mdx
+++ b/versions/8.0.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.0.1/docs/configurable-attributes.mdx b/versions/8.0.1/docs/configurable-attributes.mdx
index 7780d6d9..a13cd763 100644
--- a/versions/8.0.1/docs/configurable-attributes.mdx
+++ b/versions/8.0.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.0.1/install/ubuntu.mdx b/versions/8.0.1/install/ubuntu.mdx
index de5ea216..0884da35 100644
--- a/versions/8.0.1/install/ubuntu.mdx
+++ b/versions/8.0.1/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.0.1/release/rolling.mdx b/versions/8.0.1/release/rolling.mdx
index 42ae1e01..fc3613f9 100644
--- a/versions/8.0.1/release/rolling.mdx
+++ b/versions/8.0.1/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/8.1.1/configure/attributes.mdx b/versions/8.1.1/configure/attributes.mdx
index c28a5358..9d99de1c 100644
--- a/versions/8.1.1/configure/attributes.mdx
+++ b/versions/8.1.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.1.1/contribute/search.mdx b/versions/8.1.1/contribute/search.mdx
index 33ee794f..89e394c0 100644
--- a/versions/8.1.1/contribute/search.mdx
+++ b/versions/8.1.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.1.1/docs/configurable-attributes.mdx b/versions/8.1.1/docs/configurable-attributes.mdx
index c272fd02..9e4a30a3 100644
--- a/versions/8.1.1/docs/configurable-attributes.mdx
+++ b/versions/8.1.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.1.1/install/ubuntu.mdx b/versions/8.1.1/install/ubuntu.mdx
index c9ad913a..20d692ef 100644
--- a/versions/8.1.1/install/ubuntu.mdx
+++ b/versions/8.1.1/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.1.1/release/rolling.mdx b/versions/8.1.1/release/rolling.mdx
index c9ded870..1a7ce5aa 100644
--- a/versions/8.1.1/release/rolling.mdx
+++ b/versions/8.1.1/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/8.2.1/configure/attributes.mdx b/versions/8.2.1/configure/attributes.mdx
index bea003d1..62c4cf91 100644
--- a/versions/8.2.1/configure/attributes.mdx
+++ b/versions/8.2.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.2.1/contribute/search.mdx b/versions/8.2.1/contribute/search.mdx
index 3e0ee2a6..791dd72b 100644
--- a/versions/8.2.1/contribute/search.mdx
+++ b/versions/8.2.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
`\`
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
`\`
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.2.1/docs/configurable-attributes.mdx b/versions/8.2.1/docs/configurable-attributes.mdx
index 80e08920..9db8b8ee 100644
--- a/versions/8.2.1/docs/configurable-attributes.mdx
+++ b/versions/8.2.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.2.1/install/ubuntu.mdx b/versions/8.2.1/install/ubuntu.mdx
index 4b808714..c9ecfa05 100644
--- a/versions/8.2.1/install/ubuntu.mdx
+++ b/versions/8.2.1/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.2.1/release/rolling.mdx b/versions/8.2.1/release/rolling.mdx
index e76532dc..a616bef7 100644
--- a/versions/8.2.1/release/rolling.mdx
+++ b/versions/8.2.1/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/8.3.1/configure/attributes.mdx b/versions/8.3.1/configure/attributes.mdx
index 9234424c..cc1a8e45 100644
--- a/versions/8.3.1/configure/attributes.mdx
+++ b/versions/8.3.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.3.1/contribute/search.mdx b/versions/8.3.1/contribute/search.mdx
index 33ee794f..89e394c0 100644
--- a/versions/8.3.1/contribute/search.mdx
+++ b/versions/8.3.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.3.1/docs/configurable-attributes.mdx b/versions/8.3.1/docs/configurable-attributes.mdx
index e61a31cf..d7e6c38c 100644
--- a/versions/8.3.1/docs/configurable-attributes.mdx
+++ b/versions/8.3.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.3.1/install/ubuntu.mdx b/versions/8.3.1/install/ubuntu.mdx
index 63d2835a..8c9de2ef 100644
--- a/versions/8.3.1/install/ubuntu.mdx
+++ b/versions/8.3.1/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.3.1/release/rolling.mdx b/versions/8.3.1/release/rolling.mdx
index e8a57ef0..a9d4df5c 100644
--- a/versions/8.3.1/release/rolling.mdx
+++ b/versions/8.3.1/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/8.4.2/configure/attributes.mdx b/versions/8.4.2/configure/attributes.mdx
index c4cc4a8f..4b70c4b2 100644
--- a/versions/8.4.2/configure/attributes.mdx
+++ b/versions/8.4.2/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.4.2/contribute/search.mdx b/versions/8.4.2/contribute/search.mdx
index 33ee794f..89e394c0 100644
--- a/versions/8.4.2/contribute/search.mdx
+++ b/versions/8.4.2/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.4.2/docs/configurable-attributes.mdx b/versions/8.4.2/docs/configurable-attributes.mdx
index 728dfc9f..2f54aeb4 100644
--- a/versions/8.4.2/docs/configurable-attributes.mdx
+++ b/versions/8.4.2/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.4.2/install/ubuntu.mdx b/versions/8.4.2/install/ubuntu.mdx
index d7b4b8b5..b52c61df 100644
--- a/versions/8.4.2/install/ubuntu.mdx
+++ b/versions/8.4.2/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.4.2/release/rolling.mdx b/versions/8.4.2/release/rolling.mdx
index 4aba6ac2..059b8276 100644
--- a/versions/8.4.2/release/rolling.mdx
+++ b/versions/8.4.2/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/8.5.1/configure/attributes.mdx b/versions/8.5.1/configure/attributes.mdx
index 0ac773dc..25780646 100644
--- a/versions/8.5.1/configure/attributes.mdx
+++ b/versions/8.5.1/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.5.1/contribute/search.mdx b/versions/8.5.1/contribute/search.mdx
index 40be6720..b081e3ad 100644
--- a/versions/8.5.1/contribute/search.mdx
+++ b/versions/8.5.1/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.5.1/docs/configurable-attributes.mdx b/versions/8.5.1/docs/configurable-attributes.mdx
index 37689d4a..84eff413 100644
--- a/versions/8.5.1/docs/configurable-attributes.mdx
+++ b/versions/8.5.1/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.5.1/install/ubuntu.mdx b/versions/8.5.1/install/ubuntu.mdx
index e20b5c48..023b9539 100644
--- a/versions/8.5.1/install/ubuntu.mdx
+++ b/versions/8.5.1/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.5.1/release/rolling.mdx b/versions/8.5.1/release/rolling.mdx
index 43bdfb06..9c0ad335 100644
--- a/versions/8.5.1/release/rolling.mdx
+++ b/versions/8.5.1/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/8.6.0/configure/attributes.mdx b/versions/8.6.0/configure/attributes.mdx
index dffcfbc3..b9fde83c 100644
--- a/versions/8.6.0/configure/attributes.mdx
+++ b/versions/8.6.0/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.6.0/contribute/search.mdx b/versions/8.6.0/contribute/search.mdx
index 00ac2a00..21b9cc22 100644
--- a/versions/8.6.0/contribute/search.mdx
+++ b/versions/8.6.0/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
`\`
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
`\`
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.6.0/docs/configurable-attributes.mdx b/versions/8.6.0/docs/configurable-attributes.mdx
index fd3834d7..2049810e 100644
--- a/versions/8.6.0/docs/configurable-attributes.mdx
+++ b/versions/8.6.0/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/8.6.0/release/rolling.mdx b/versions/8.6.0/release/rolling.mdx
index 4ab04980..718bbdf4 100644
--- a/versions/8.6.0/release/rolling.mdx
+++ b/versions/8.6.0/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index
-
+
diff --git a/versions/8.7.0/configure/attributes.mdx b/versions/8.7.0/configure/attributes.mdx
index 789c1d9e..3df895c4 100644
--- a/versions/8.7.0/configure/attributes.mdx
+++ b/versions/8.7.0/configure/attributes.mdx
@@ -43,7 +43,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/8.7.0/contribute/search.mdx b/versions/8.7.0/contribute/search.mdx
index 60bc67e8..e72d9cf2 100644
--- a/versions/8.7.0/contribute/search.mdx
+++ b/versions/8.7.0/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/8.7.0/docs/configurable-attributes.mdx b/versions/8.7.0/docs/configurable-attributes.mdx
index 0363a963..4cfd1a35 100644
--- a/versions/8.7.0/docs/configurable-attributes.mdx
+++ b/versions/8.7.0/docs/configurable-attributes.mdx
@@ -43,7 +43,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
diff --git a/versions/8.7.0/install/ubuntu.mdx b/versions/8.7.0/install/ubuntu.mdx
index 25cb472d..1820abdb 100644
--- a/versions/8.7.0/install/ubuntu.mdx
+++ b/versions/8.7.0/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/8.7.0/release/rolling.mdx b/versions/8.7.0/release/rolling.mdx
index 6e53cc6f..48b26e37 100644
--- a/versions/8.7.0/release/rolling.mdx
+++ b/versions/8.7.0/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/9.0.0/configure/attributes.mdx b/versions/9.0.0/configure/attributes.mdx
index 2ac9d741..8bcd5bc2 100644
--- a/versions/9.0.0/configure/attributes.mdx
+++ b/versions/9.0.0/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/9.0.0/contribute/search.mdx b/versions/9.0.0/contribute/search.mdx
index 50dc4164..9a721b88 100644
--- a/versions/9.0.0/contribute/search.mdx
+++ b/versions/9.0.0/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
\
-
-
Escapes special characters, such as ., \, or (.
-
run\(\)
+
\
+
+
Escapes special characters, such as ., \, or (.
+
run\(\)
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/9.0.0/docs/configurable-attributes.mdx b/versions/9.0.0/docs/configurable-attributes.mdx
index 9f7f0a6c..ba33ddb0 100644
--- a/versions/9.0.0/docs/configurable-attributes.mdx
+++ b/versions/9.0.0/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/9.0.0/external/migration_tool.mdx b/versions/9.0.0/external/migration_tool.mdx
index 195f2b57..3cdaaf34 100644
--- a/versions/9.0.0/external/migration_tool.mdx
+++ b/versions/9.0.0/external/migration_tool.mdx
@@ -68,7 +68,7 @@ Before you begin:
Once the prerequisites are met, run the following commands to use the migration
tool:
-
+
# Clone the Bazel Central Registry repository
git clone https://github.com/bazelbuild/bazel-central-registry.git
cd bazel-central-registry
@@ -125,7 +125,7 @@ To see the migration script in action, consider the following scenario when
Python, Maven and Go dependencies are declared in `WORKSPACE` file.
-
+
Click here to see `WORKSPACE` file
@@ -265,7 +265,7 @@ Moreover, to demonstrate usage of module extension, custom macro is invoked from
`WORKSPACE` and it is defined in `my_custom_macro.bzl`.
-
+
Click here to see `my_custom_macro.bzl` file
@@ -302,27 +302,27 @@ The first step is to follow [How to Use the Migration Tool](#migration-tool-how-
Then, running `migrate2bzlmod -t=//...` outputs:
-
+
bazel 7.6.1
Generating ./resolved_deps.py file - It might take a while...
- RESOLVED:rules_java has been introduced as a Bazel module.
- RESOLVED:bazel_gazelle has been introduced as a Bazel module.
- RESOLVED:io_bazel_rules_go has been introduced as a Bazel module.
- RESOLVED:rules_python has been introduced as a Bazel module.
- IMPORTANT: 3.11 is used as a default python version. If you need a different version, please change it manually and then rerun the migration tool.
- RESOLVED:my_python_deps has been introduced as python extension.
- RESOLVED:org_golang_x_net has been introduced as go extension.
- RESOLVED:rules_jvm_external has been introduced as a Bazel module.
- RESOLVED:org.antlr has been introduced as maven extension.
- RESOLVED:rules_shell has been introduced as a Bazel module.
+ RESOLVED:rules_java has been introduced as a Bazel module.
+ RESOLVED:bazel_gazelle has been introduced as a Bazel module.
+ RESOLVED:io_bazel_rules_go has been introduced as a Bazel module.
+ RESOLVED:rules_python has been introduced as a Bazel module.
+ IMPORTANT: 3.11 is used as a default python version. If you need a different version, please change it manually and then rerun the migration tool.
+ RESOLVED:my_python_deps has been introduced as python extension.
+ RESOLVED:org_golang_x_net has been introduced as go extension.
+ RESOLVED:rules_jvm_external has been introduced as a Bazel module.
+ RESOLVED:org.antlr has been introduced as maven extension.
+ RESOLVED:rules_shell has been introduced as a Bazel module.
Congratulations! All external repositories needed for building //... are available with Bzlmod!
- IMPORTANT: Fix potential build time issues by running the following command:
- bazel build --enable_bzlmod --noenable_workspace //...
+ IMPORTANT: Fix potential build time issues by running the following command:
+ bazel build --enable_bzlmod --noenable_workspace //...
- IMPORTANT:For details about the migration process, check `migration_info.md` file.
+ IMPORTANT:For details about the migration process, check `migration_info.md` file.
which gives the following important information:
@@ -344,10 +344,10 @@ which gives the following important information:
This section illustrates the migration of code from the `WORKSPACE` file to
`MODULE.bazel`.
-
-
+
## Tips with debugging {#migration-tool-tips}
@@ -639,7 +639,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
declared in the `WORKSPACE` file, which is particularly useful for the
debugging. You can see it as:
-
+
> Click here to see where and how the repo was declared in the WORKSPACE
file
@@ -648,7 +648,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
earlier [Migration Example](#migration-tool-example), that would look as:
1. Bazel module Dependency - `Migration of rules_python`
-
+
Found perfect name match in BCR: rules_python
Found partially name matches in BCR: rules_python_gazelle_plugin
@@ -661,7 +661,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
added.
2. Python extension - `Migration of my_python_deps`
-
+
pip.parse(
hub_name = "my_python_deps",
requirements_lock = "//:requirements_lock.txt",
@@ -672,7 +672,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
3. Maven extension - `Migration of org.antlr (px_deps):`
-
+
maven.artifact(
name = "px_deps",
group = "org.antlr",
@@ -683,7 +683,7 @@ from scratch if it's the first run or if the [`--i` flag](#migration-script-flag
4. Go extension - `Migration of org_golang_x_net`
-
+
+
+ Graph After Resolution
{/* digraph mygraph {
node [ shape=box ]
diff --git a/versions/9.0.0/install/ubuntu.mdx b/versions/9.0.0/install/ubuntu.mdx
index 79fd59b3..0b3ef32c 100644
--- a/versions/9.0.0/install/ubuntu.mdx
+++ b/versions/9.0.0/install/ubuntu.mdx
@@ -41,7 +41,7 @@ Bazel comes with two completion scripts. After installing Bazel, you can:
```posix-terminal
sudo apt install apt-transport-https curl gnupg -y
-curl -fsSL https://releases.bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
+curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
diff --git a/versions/9.0.0/release/rolling.mdx b/versions/9.0.0/release/rolling.mdx
index 8aaeb725..f158f563 100644
--- a/versions/9.0.0/release/rolling.mdx
+++ b/versions/9.0.0/release/rolling.mdx
@@ -9,4 +9,4 @@ these releases.
## Index {#index}
-
+
diff --git a/versions/9.1.0/configure/attributes.mdx b/versions/9.1.0/configure/attributes.mdx
index 2be60baf..61e430a1 100644
--- a/versions/9.1.0/configure/attributes.mdx
+++ b/versions/9.1.0/configure/attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/9.1.0/contribute/search.mdx b/versions/9.1.0/contribute/search.mdx
index 479bfa87..704c230b 100644
--- a/versions/9.1.0/contribute/search.mdx
+++ b/versions/9.1.0/contribute/search.mdx
@@ -210,62 +210,62 @@ You can refine your search using the following filters.
-
Filter
-
Other options
-
Description
-
Example
+
Filter
+
Other options
+
Description
+
Example
-
lang:
-
language:
-
Perform an exact match by file language.
-
lang:java test
+
lang:
+
language:
+
Perform an exact match by file language.
+
lang:java test
-
file:
-
filepath:
+
file:
+
filepath:
path:
f:
-
-
+
+
-
case:yes
-
-
Make the search case sensitive. By default, searches are not case-sensitive.
-
case:yes Hello World
+
case:yes
+
+
Make the search case sensitive. By default, searches are not case-sensitive.
+
case:yes Hello World
-
class:
-
-
Search for a class name.
-
class:MainClass
+
class:
+
+
Search for a class name.
+
class:MainClass
-
function:
-
func:
-
Search for a function name.
-
function:print
+
function:
+
func:
+
Search for a function name.
+
function:print
-
-
-
-
Negates the term from the search.
-
hello -world
+
-
+
+
Negates the term from the search.
+
hello -world
-
`\`
-
-
Escapes special characters, such as ., \, or (.
-
`run\(\)`
+
`\`
+
+
Escapes special characters, such as ., \, or (.
+
`run\(\)`
-
"[term]"
-
-
Perform a literal search.
-
"class:main"
+
"[term]"
+
+
Perform a literal search.
+
"class:main"
diff --git a/versions/9.1.0/docs/configurable-attributes.mdx b/versions/9.1.0/docs/configurable-attributes.mdx
index 1321a961..c1400eca 100644
--- a/versions/9.1.0/docs/configurable-attributes.mdx
+++ b/versions/9.1.0/docs/configurable-attributes.mdx
@@ -42,7 +42,7 @@ This declares a `cc_binary` that "chooses" its deps based on the flags at the
command line. Specifically, `deps` becomes:
-
+
Command
deps =
diff --git a/versions/9.1.0/external/migration_tool.mdx b/versions/9.1.0/external/migration_tool.mdx
index 0d98e263..ed2250c9 100644
--- a/versions/9.1.0/external/migration_tool.mdx
+++ b/versions/9.1.0/external/migration_tool.mdx
@@ -68,7 +68,7 @@ Before you begin:
Once the prerequisites are met, run the following commands to use the migration
tool:
-
+
# Clone the Bazel Central Registry repository
git clone https://github.com/bazelbuild/bazel-central-registry.git
cd bazel-central-registry
@@ -126,7 +126,7 @@ To see the migration script in action, consider the following scenario when
Python, Maven and Go dependencies are declared in `WORKSPACE` file.
-
+
Click here to see `WORKSPACE` file
@@ -266,7 +266,7 @@ Moreover, to demonstrate usage of module extension, custom macro is invoked from
`WORKSPACE` and it is defined in `my_custom_macro.bzl`.
-
+
Click here to see `my_custom_macro.bzl` file
@@ -304,27 +304,27 @@ Tool](#migration-tool-how-to-use), which mostly is checking the bazel version
Then, running `migrate2bzlmod -t=//...` outputs:
-
+
bazel 7.6.1
Generating ./resolved_deps.py file - It might take a while...
- RESOLVED:rules_java has been introduced as a Bazel module.
- RESOLVED:bazel_gazelle has been introduced as a Bazel module.
- RESOLVED:io_bazel_rules_go has been introduced as a Bazel module.
- RESOLVED:rules_python has been introduced as a Bazel module.
- IMPORTANT: 3.11 is used as a default python version. If you need a different version, please change it manually and then rerun the migration tool.
- RESOLVED:my_python_deps has been introduced as python extension.
- RESOLVED:org_golang_x_net has been introduced as go extension.
- RESOLVED:rules_jvm_external has been introduced as a Bazel module.
- RESOLVED:org.antlr has been introduced as maven extension.
- RESOLVED:rules_shell has been introduced as a Bazel module.
+ RESOLVED:rules_java has been introduced as a Bazel module.
+ RESOLVED:bazel_gazelle has been introduced as a Bazel module.
+ RESOLVED:io_bazel_rules_go has been introduced as a Bazel module.
+ RESOLVED:rules_python has been introduced as a Bazel module.
+ IMPORTANT: 3.11 is used as a default python version. If you need a different version, please change it manually and then rerun the migration tool.
+ RESOLVED:my_python_deps has been introduced as python extension.
+ RESOLVED:org_golang_x_net has been introduced as go extension.
+ RESOLVED:rules_jvm_external has been introduced as a Bazel module.
+ RESOLVED:org.antlr has been introduced as maven extension.
+ RESOLVED:rules_shell has been introduced as a Bazel module.
Congratulations! All external repositories needed for building //... are available with Bzlmod!
- IMPORTANT: Fix potential build time issues by running the following command:
- bazel build --enable_bzlmod --noenable_workspace //...
+ IMPORTANT: Fix potential build time issues by running the following command:
+ bazel build --enable_bzlmod --noenable_workspace //...
- IMPORTANT:For details about the migration process, check `migration_info.md` file.
+ IMPORTANT:For details about the migration process, check `migration_info.md` file.
which gives the following important information:
@@ -346,10 +346,10 @@ which gives the following important information:
This section illustrates the migration of code from the `WORKSPACE` file to
`MODULE.bazel`.
-
-
+
## Tips with debugging {#migration-tool-tips}
@@ -642,7 +642,7 @@ flag](#migration-script-flags) is used. The report contains:
declared in the `WORKSPACE` file, which is particularly useful for the
debugging. You can see it as:
-
+
> Click here to see where and how the repo was declared in the WORKSPACE
file
@@ -651,7 +651,7 @@ flag](#migration-script-flags) is used. The report contains:
earlier [Migration Example](#migration-tool-example), that would look as:
1. Bazel module Dependency - `Migration of rules_python`
-
+
Found perfect name match in BCR: rules_python
Found partially name matches in BCR: rules_python_gazelle_plugin
@@ -664,7 +664,7 @@ flag](#migration-script-flags) is used. The report contains:
added.
2. Python extension - `Migration of my_python_deps`
-
+
pip.parse(
hub_name = "my_python_deps",
requirements_lock = "//:requirements_lock.txt",
@@ -675,7 +675,7 @@ flag](#migration-script-flags) is used. The report contains:
3. Maven extension - `Migration of org.antlr (px_deps):`
-
+
maven.artifact(
name = "px_deps",
group = "org.antlr",
@@ -686,7 +686,7 @@ flag](#migration-script-flags) is used. The report contains:
4. Go extension - `Migration of org_golang_x_net`
-