)]}' { "log": [ { "commit": "bb4e9e8cf14511e7b9cf7bda3d1c1f277d076e24", "tree": "7365fabe1fc41fd7a10f51e3dc295b256f8fd8f0", "parents": [ "226c4886e9243e9b6045ce4adb7e6c1bb6a4ab07" ], "author": { "name": "Takeshi Yoneda", "email": "t.y.mathetake@gmail.com", "time": "Fri Aug 07 16:36:54 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Aug 07 16:36:54 2026" }, "message": "Fixes lockfile checksum for non-root repo (#3866)\n\nFixes https://github.com/bazelbuild/rules_rust/issues/3521\n\n---------\n\nSigned-off-by: Takeshi Yoneda \u003ctyoneda@netflix.com\u003e\nSigned-off-by: Takeshi Yoneda \u003ct.y.mathetake@gmail.com\u003e\nCo-authored-by: UebelAndre \u003cgithub@uebelandre.com\u003e" }, { "commit": "226c4886e9243e9b6045ce4adb7e6c1bb6a4ab07", "tree": "143c4fa7611d58a2f23ef1fe3333334cd1f4ff9c", "parents": [ "b0076d5cd925634c01fadb1090a212f2bd307c41" ], "author": { "name": "Finn Ball", "email": "finn.ball@codificasolutions.com", "time": "Wed Aug 05 13:31:54 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Aug 05 13:31:54 2026" }, "message": "Include link_deps in Rust runfiles (#4204)\n\n## Summary\n\n- merge default runfiles from `link_deps` into Rust target runfiles\n- include dynamic libraries supplied through `link_deps` alongside those\nfrom `deps`\n\n## Why\n\n`link_deps` participates in native linking, but its runfiles and dynamic\nlibraries were omitted when `rustc_compile_action` assembled runtime\nfiles. Binaries and library targets that link native dependencies\nthrough `link_deps` could therefore be built successfully while missing\nrequired runtime artifacts.\n\n## Impact\n\nRust binaries, `cdylib`s, and `staticlib`s now carry the runtime files\nneeded by dependencies declared through `link_deps`.\n\n## Validation\n\n- `bazel test //test/unit/link_deps:all`\n- `git diff --check`" }, { "commit": "b0076d5cd925634c01fadb1090a212f2bd307c41", "tree": "febe6c0d50e06109b6532afec062454b02558467", "parents": [ "4e0d17a23e440daf108eb611edfe713d297de032" ], "author": { "name": "Jorge Gorbe Moya", "email": "slack@codemaniacs.com", "time": "Tue Aug 04 15:56:02 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Aug 04 15:56:02 2026" }, "message": "Check for nightly toolchain when enabling split debug info. (#4186)\n\nThis fixes a problem pointed out by\n\nhttps://github.com/bazelbuild/rules_rust/pull/4092#issuecomment-5136906807.\n\n`-Zsplit-dwarf-out-dir` is only available on nightly, so we have to gate\nsplit debug info on it. Now, if the user requests `--fission` while\nusing a non-nightly Rust toolchain, the build will fail. To avoid\nbreaking users relying on the previous behavior, a\n`skip_fission_for_rust` flag has been added. Users can add it to their\nbazelrc file to explicitly signal that they\u0027re okay with Rust compiles\nnot producing split debug info, even if requested in the command line.\n\nAssisted-by: Gemini" }, { "commit": "4e0d17a23e440daf108eb611edfe713d297de032", "tree": "ddfa5fe02b7a01a0a327ff199a9ef6db23ff70fa", "parents": [ "60231db04d16432f9fef673765cb11cd7e6f1a61" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Aug 03 14:32:40 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Aug 03 14:32:40 2026" }, "message": "Fix release notes (#4174)\n\nI\u0027ve had to go back and manually edit it so did a pass to update it a\nbit and make sure it renders correctly" }, { "commit": "60231db04d16432f9fef673765cb11cd7e6f1a61", "tree": "12836733b6de67d9bb76147125e0b25ac01a1f3c", "parents": [ "d7c7117399990e73fd12964d7ea2c78967aa210e" ], "author": { "name": "Finn Ball", "email": "finn.ball@codificasolutions.com", "time": "Fri Jul 31 17:55:06 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 31 17:55:06 2026" }, "message": "Release 0.73.0 (#4187)" }, { "commit": "d7c7117399990e73fd12964d7ea2c78967aa210e", "tree": "2643ca813cf10ec94789c415700d2c908ae7fc26", "parents": [ "ea0592c50fd437dc07cec6f757f3010ede156f7a" ], "author": { "name": "Finn Ball", "email": "finn.ball@codificasolutions.com", "time": "Fri Jul 31 15:07:23 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 31 15:07:23 2026" }, "message": "Add build_script_env_files crate annotation (#4166)\n\n## Summary\n\nAdd `build_script_env_files` support to `crate.annotation`, allowing\nenvironment files to be passed to generated `cargo_build_script`\ntargets.\n\nThe change:\n\n- Exposes `build_script_env_files` through bzlmod and legacy crate\nannotations.\n- Propagates the annotation through crate-universe configuration and\nbuild-script context.\n- Renders the attribute on generated `cargo_build_script` rules.\n- Supports unconditional and platform-selected values.\n- Updates the configuration digest.\n- Adds tests for annotation propagation and BUILD-file rendering.\n\n## Testing\n\n- `bazel test //crate_universe:unit_test`" }, { "commit": "ea0592c50fd437dc07cec6f757f3010ede156f7a", "tree": "971a4fa31961b08770213cdee002af4a0f3ed72e", "parents": [ "02749ca8edc37e56a1ad33deaea2eed9cc719ade" ], "author": { "name": "FabianWolff", "email": "16052130+FabianWolff@users.noreply.github.com", "time": "Fri Jul 31 14:50:52 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 31 14:50:52 2026" }, "message": "Set `toolchain` parameter to `toolchain_type` instead of `None` (#4185)\n\nI don\u0027t understand the exact mechanics of this, but it appears to be\nnecessary to support multiple different exec configurations." }, { "commit": "02749ca8edc37e56a1ad33deaea2eed9cc719ade", "tree": "934cc5ee4f075b0c475bc0ffe6d15d132ed02259", "parents": [ "d6e7cc353b126000a39b497b6acf9b23b712d7f6" ], "author": { "name": "Georges Farah", "email": "georges.farah@datadoghq.com", "time": "Thu Jul 30 18:54:22 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 30 18:54:22 2026" }, "message": "fix(crate_universe): pass OUTPUT_BASE as --output_base startup flag to bazel info (#4183)\n\n## Problem\n\nThe `OUTPUT_BASE` env var was added to let CI environments supply the\noutput_base without relying on `bazel info`. However, the override is\napplied **after** parsing the `bazel info` output:\n\n```rust\nlet output \u003d process::Command::new(bazel).arg(\"info\")...output()?;\nif !output.status.success() {\n bail!(output.status) // \u003c-- bails here when output_base is not writable\n}\n// ... parse output ...\nif let Ok(path) \u003d env::var(\"OUTPUT_BASE\") { // \u003c-- never reached\n bazel_info.insert(...);\n}\n```\n\nWhen `bazel info` fails (e.g. the default `~/.cache/bazel/...` is not\nwritable in a sandboxed CI), the function bails before `OUTPUT_BASE` is\never checked — making the env var useless for its intended purpose.\n\n## Fix\n\nPass `OUTPUT_BASE` as a `--output_base` Bazel **startup flag** (before\nthe subcommand):\n\n```\nbazel --output_base\u003d/path/to/base info release output_base\n```\n\nStartup flags take effect before Bazel accesses any path, so it never\ntouches the default (possibly non-writable) output_base. The `bazel\ninfo` subprocess runs normally and the post-parsing override is no\nlonger needed.\n\n## Changes\n\n- `crate_universe/src/cli/vendor.rs`: restructure `BazelInfo::try_new`\nto optionally inject `--output_base` as a startup flag; remove the\npost-parsing `OUTPUT_BASE` override.\n- Removed `test_parse_bazel_info_output_base_env_override` since\n`parse_bazel_info` no longer handles the `OUTPUT_BASE` override — the\nexisting `test_bazel_info` already covers the parsing logic." }, { "commit": "d6e7cc353b126000a39b497b6acf9b23b712d7f6", "tree": "6cc6d9bf0f063780563b95acfe5e16f9049d5300", "parents": [ "b88f87a6148db823b409b235e27ea0950760ad2c" ], "author": { "name": "Cameron Mulhern", "email": "csmulhern@gmail.com", "time": "Thu Jul 30 18:01:59 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 30 18:01:59 2026" }, "message": "Stabilizes per_crate_rustc_flag (#4182)\n\nFixes #1711." }, { "commit": "b88f87a6148db823b409b235e27ea0950760ad2c", "tree": "e5037c4a88f8df8c42e9d6455cc29d68a64152af", "parents": [ "8bad538608529bf24e4ef6e4ced97ade05b66b4e" ], "author": { "name": "Georges Farah", "email": "georges.farah2114@gmail.com", "time": "Thu Jul 30 15:01:25 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 30 15:01:25 2026" }, "message": "fix(crate_universe): fix OUTPUT_BASE env var value format in crates_vendor (#4102)\n\n## Summary\n\nFix the `OUTPUT_BASE` environment variable override in\n`crate_universe/src/cli/vendor.rs` — it has never worked correctly.\n\n## Bug\n\nThe `bazel info` output parser splits each line on `:` and stores only\nthe part after the colon as the HashMap value:\n\n```rust\nlet (k, v) \u003d line.split_at(line.find(\u0027:\u0027)?);\nOk((k.to_string(), (v[1..]).trim().to_string()))\n```\n\nSo for output like `output_base: /data/output`, the HashMap contains\n`{\"output_base\" \u003d\u003e \"/data/output\"}`.\n\nHowever, the `OUTPUT_BASE` env var override stores the **full formatted\nstring** as the value:\n\n```rust\nbazel_info.insert(\"output_base\".to_owned(), format!(\"output_base: {}\", path));\n```\n\nThis produces `{\"output_base\" \u003d\u003e \"output_base: /data/output\"}`. When\n`TryFrom` later converts this to a `PathBuf` via `.map(Into::into)`, it\nproduces `PathBuf(\"output_base: /data/output\")` — an invalid path.\n\n## Fix\n\nStore the raw path string without the prefix:\n\n```rust\nbazel_info.insert(\"output_base\".to_owned(), path);\n```\n\nAlso extract `parse_bazel_info` from `try_new` so the parsing and env\nvar override logic can be unit-tested without spawning a `bazel info`\nsubprocess.\n\n## Test plan\n\nAdded `test_parse_bazel_info_output_base_env_override` which verifies:\n- Without `OUTPUT_BASE` set, the parsed value from `bazel info` output\nis used\n- With `OUTPUT_BASE` set, it overrides the parsed value with the correct\npath\n\n## Note\n\nThe test uses `env::set_var`/`env::remove_var`, which are `unsafe` in\nRust 1.83+ (and required to be in `unsafe` blocks starting with edition\n2024). This matches the existing test style in this file (see\n`test_bazel_info`). A follow-up could migrate both tests to use `unsafe\n{}` blocks or `#[serial_test::serial]` if the project upgrades its Rust\nedition.\n\nCo-authored-by: UebelAndre \u003cgithub@uebelandre.com\u003e" }, { "commit": "8bad538608529bf24e4ef6e4ced97ade05b66b4e", "tree": "98bd1331436c759e3aecadfebd786690f0f5fc26", "parents": [ "48b42911a97f837061b99a0b93f0f48190e8f15b" ], "author": { "name": "Georges Farah", "email": "georges.farah2114@gmail.com", "time": "Thu Jul 30 14:19:11 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 30 14:19:11 2026" }, "message": "release: remove WORKSPACE snippets from release notes template (#4180)\n\n## Summary\n\nWORKSPACE support was removed in #4005 (released in 0.71.0). The release\nnotes template was not updated at the time, so every release since\n0.71.0 (0.71.0, 0.71.1, 0.71.2, 0.71.3, 0.72.0) has advertised\n`http_archive` WORKSPACE snippets that don\u0027t work.\n\nThis removes all WORKSPACE sections from the template so future release\nnotes only show the Bzlmod setup.\n\nAlso fixes a pre-existing missing `\u003c/details\u003e` closing tag in the Prost\nextension section." }, { "commit": "48b42911a97f837061b99a0b93f0f48190e8f15b", "tree": "8ab53cc298087fca0ff42ca259a9428ce55fcdc2", "parents": [ "6da7aa0442c1f79194ffff1300face951d42ccb9" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 27 17:51:03 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 17:51:03 2026" }, "message": "Release 0.72.0 (#4171)" }, { "commit": "6da7aa0442c1f79194ffff1300face951d42ccb9", "tree": "3b0d7104200f556b9c19eb90c43d1afa4a24b7f2", "parents": [ "618c0916a358db1db5ac0ef608ff34d7d77ec303" ], "author": { "name": "Xiaoyi", "email": "ashi009@users.noreply.github.com", "time": "Mon Jul 27 17:26:44 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 17:26:44 2026" }, "message": "crate_universe: move build-script dep to extra_deps (#4090)\n\nFixes #4089.\n\nA crate with a build script depends on its own `build_script_build`\ntarget. That edge was stored in `common_attrs.deps`, which\n`Context::workspace_member_deps()` collects to emit crate-hub aliases —\nso a library crate with a build script got a dead crate-hub alias for\nitself.\n\nStore the edge in `common_attrs.extra_deps` instead:\n`workspace_member_deps()` does not read `extra_deps`, so the\nself-reference no longer yields an alias. (`extra_deps` holds resolved\nlabels, so the edge becomes a relative `:build_script_build` — same\ntarget, same package.)\n\nCo-authored-by: UebelAndre \u003cgithub@uebelandre.com\u003e" }, { "commit": "618c0916a358db1db5ac0ef608ff34d7d77ec303", "tree": "88119669af5ab6dd60977744752630a1e53124ba", "parents": [ "a0633ba25adea1b82830d189149746b07170366d" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 27 17:25:00 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 17:25:00 2026" }, "message": "Respect `--instrumentation_filer` for Rust coverage (#4173)\n\nre-implements https://github.com/bazelbuild/rules_rust/pull/4013\n\nFull credits to @tamasvajk. Thank you so much!" }, { "commit": "a0633ba25adea1b82830d189149746b07170366d", "tree": "df8710eea48b43941e0af860fec01c5866a69fe9", "parents": [ "4a67cca2dfc43f173581a0cfe31b4c1138727e9d" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 27 16:54:09 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 16:54:09 2026" }, "message": "Avoid force excluding `bazel-*` in vscode (#4169)\n\nWe shouldn\u0027t blanket exclude `bazel-*` so users can continue to inspect\nthese directories in the file browser." }, { "commit": "4a67cca2dfc43f173581a0cfe31b4c1138727e9d", "tree": "b355de8054ec39af8bd4f38211fa65cd8d65df89", "parents": [ "e468ae28638506715ab9ab25305f46292273904d" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 27 16:14:05 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 16:14:05 2026" }, "message": "Propagate wasm runfiles (#4168)\n\nThis change allows the wasm targets to propagate runfiles with the\nbindgen outputs." }, { "commit": "e468ae28638506715ab9ab25305f46292273904d", "tree": "5ba8b6f3badecadc1bf0fb6e75313a898d40ed19", "parents": [ "8ad225a81487f5b4fa00dce91ad99cfa14da1db5" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 27 16:06:49 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 16:06:49 2026" }, "message": "Fix crate_universe deps interface (#4134)\n\nThis change updates the deps interface to refer to the\n`crates_vendor_remote_repository` repository.\n\ncloses https://github.com/bazelbuild/rules_rust/issues/4132" }, { "commit": "8ad225a81487f5b4fa00dce91ad99cfa14da1db5", "tree": "b7a12973ef86b8031d412c1df590117cf9ea5b00", "parents": [ "6503de22ca3fb4c5b04c81d5d97c9f0a0d7f6b3a" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 27 15:26:57 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 15:26:57 2026" }, "message": "Add `RunfilesBuilder` to runfiles (#4170)\n\nThis change aims to enable the use of the runfiles library on\nenvironments like `wasm` where `fs` and `env` support is limited. The\nbuilder allows for more explicit control over the construction of a\n`Runfiles` instance." }, { "commit": "6503de22ca3fb4c5b04c81d5d97c9f0a0d7f6b3a", "tree": "a570b58411a082a311803c5d9e3355fa1088caaf", "parents": [ "5f04c8c14c2ffacfe10ad14e55298be21454be04" ], "author": { "name": "Jakob Koschel", "email": "jakobkoschel@google.com", "time": "Mon Jul 27 15:20:39 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 27 15:20:39 2026" }, "message": "Handle PIC/NOPIC correctly in establish_cc_info (#4131)\n\nThis change determines whether to use `pic_static_library` or\n`static_library` in `cc_common.create_library_to_link` based on the\n`should_use_pic` helper. It also updates the unit tests to expect only\none of the libraries depending on the configuration.\n\nCo-authored-by: UebelAndre \u003cgithub@uebelandre.com\u003e" }, { "commit": "5f04c8c14c2ffacfe10ad14e55298be21454be04", "tree": "61e49d85a611d3273212ec2fb2db1d46306a9762", "parents": [ "0c5c01d9ec017c622c99c11df717b7464e99347c" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Fri Jul 24 09:14:57 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 24 09:14:57 2026" }, "message": "Add `cargo_build_script.use_cc_toolchain` (#4161)\n\nThis change introduces `use_cc_toolchain` to `cargo_build_script` which\ncan be used to control whether or not a `cc_toolchain` is explicitly\nwithheld from `CargoBuildScript` actions. Additionally a global flag\n`--@rules_rust//cargo/settings:use_cc_toolchain` can be used to control\nthe default of any build script that has not either explicitly set\n`use_cc_toolchain \u003d 1` (always include cc toolchains) or\n`use_cc_toolchain \u003d 0` (always exclude cc toolchains).\n\ncloses https://github.com/bazelbuild/rules_rust/issues/3680\ncloses https://github.com/bazelbuild/rules_rust/pull/3679\n\nCo-authored-by: Krasimir Georgiev \u003ckrasimir@google.com\u003e" }, { "commit": "0c5c01d9ec017c622c99c11df717b7464e99347c", "tree": "e81fe649b82b75c2404db8229a042ea0decb3a0b", "parents": [ "e65f64b8b9e76064d2ec22d057200e4209582c27" ], "author": { "name": "Krasimir Georgiev", "email": "krasimir@google.com", "time": "Thu Jul 23 15:18:38 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 23 15:18:38 2026" }, "message": "deprecate force_all_deps_direct in favor of extra_named_deps (#4160)\n\nThis is intended to give better control and more flexibility for\nextensions like Crubit, which automatically generates rust bindings for\nC++ code. The bindings generator uses an aspect to crawl over a\ndependency graph of cc_libraries, plugs itself as a tool similar to a\nC++ compiler, parses the header files and generates the corresponding\nRust bindings.\nDue to the C++ compilation model, it\u0027s possible that a header file in a\nlibrary uses a C++ symbol that is only defined in a header file owned by\nan indirect dependency of a c++ library. For example:\n\n```\nrust_library(name \u003d \"a\", hdrs \u003d [\"a.h\"])\nrust_library(name \u003d \"b\", hdrs \u003d [\"b.h\"], deps \u003d [\"a\"]) \nrust_library(name \u003d \"c\", hdrs \u003d [\"c.h\"], deps \u003d [\"b\"])\n\n# c.h\nusing C \u003d int;\n# a.h\nC f();\n```\n\nWhile compiling the generated Rust bindings of `c`, the Rust compiler\nneeds access to the generated Rust bindings of `a`, which is an indirect\ndependency. Historically, this was achieved via the\n`force_all_deps_direct` feature, which has the effect of putting all\ndirect and indirect crate dependencies as `--extern` while compiling the\nbindings for a c++ target. This is imprecise and suffers from crate name\ncollisions.\n\nIt is imprecise, because if any cc_library happens to depend on a rust\nlibrary as an implementation detail, that rust library does not need to\nbe made available via `--extern`.\n\nIt suffers from crate name collisions, because by default the crate\nnames of generated bindings are derived from the name of the label of\nthe c++ library. In a build graph where where two c++ libraries from\ndifferent packages share the same name, there is a naming collision when\nclient bindings are compiled:\n```\n# the generated bindings of both //p:a and //q:a produce a crate named a.\ncc_library(name \u003d \"client\", deps \u003d [\"//p:a\", \"//q:a\"])\n```\nTo handle these, we provide `extra_named_deps` a mechanism for\nextensions calling `rustc_compile_action` to supply an extra `depset` of\nnamed dependencies. The Crubit aspect can then compute appropriate names\nfor the generated bindings of dependencies. For this to work at scale,\nwe supply this as a depset to be computed recursively by the aspect\ncrawling the dependency graph, avoiding quadratic blaze analysis time\noverhead.\n\nThe supplied test is a mock of the type of code pattern possible in this\ncontext -- a chain of 3 rust libraries, where the top-level one refers\nto its indirect dependency via a custom crate name." }, { "commit": "e65f64b8b9e76064d2ec22d057200e4209582c27", "tree": "ed851ebfaabef577abf1657b7b27829cdc5e228b", "parents": [ "9c1dcbbcc87e6cf2f80ed2bebde8f6c163ca50c7" ], "author": { "name": "Krasimir Georgiev", "email": "krasimir@google.com", "time": "Wed Jul 22 18:49:20 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jul 22 18:49:20 2026" }, "message": "add a docstring for _get_crate_root_path (no functional changes intended) (#4162)" }, { "commit": "9c1dcbbcc87e6cf2f80ed2bebde8f6c163ca50c7", "tree": "9c392ec9f67e369017cf86c437532c2dc0ede0bb", "parents": [ "a700d1ab5a6897a11edfdeb8f5a4ae2473b9b404" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Tue Jul 21 16:01:37 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jul 21 16:01:37 2026" }, "message": "Fix NoneType error in rustdoc (#4159)\n\nThere seemed to be a confusion around `CrateInfo.output` being optional\nwithin the rustdoc rules that leads to a `NoneType` error when using\nrustdoc on a generated crate root:\n```\nexternal/rules_rust+/rust/private/rustc.bzl:1090:38: Traceback (most recent call last):\nFile \"external/rules_rust+/rust/private/rustc.bzl\", line 2883, column 16, in _get_dirname\n return file.dirname\nError: \u0027NoneType\u0027 value has no field or method \u0027dirname\u0027\n```\n\nThis change adds a proper output to satisfy the the current `CrateInfo`\ninterface." }, { "commit": "a700d1ab5a6897a11edfdeb8f5a4ae2473b9b404", "tree": "227edc9096ee349f5e4871486e43d66b04301329", "parents": [ "7a7ea1c3b4f2c510d023b6421d18dfb5546e5175" ], "author": { "name": "Krasimir Georgiev", "email": "krasimir@google.com", "time": "Tue Jul 21 11:07:36 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jul 21 11:07:36 2026" }, "message": "Add `root_path` attribute for directory crate roots (#4142)\n\nAllows specifying `root_path` when the crate root (`srcs` entrypoint) is\na directory artifact (`TreeArtifact`). This enables rules_rust targets\n(`rust_library`, `rust_binary`, `rust_test`, etc.) to consume directory\nartifacts produced by upstream rules and correctly construct the path to\nthe crate root (`lib.rs` / `main.rs`).\n\nWe use something like this internally to build standard libraries from\nsources distributed as .zip source archives: a custom rule extracts the\ncontents into a generated directory artifact, which then the rust rules\ncan consume as sources.\n\nThis may be helpful to achieve the request from\nhttps://github.com/bazelbuild/rules_rust/issues/3757, where the user is\ntrying to consume a directory of generated sources.\n\n* Adds `root_path` attribute to `_COMMON_ATTRS` and `CrateInfo`\nprovider.\n* Updates `rustc_compile_action` argument construction (`rustc.bzl`) to\njoin `crate_info.root.path` with `root_path` when\n`crate_info.root.is_directory` is true.\n* Adds a unit and build test case under `test/root_path/` using a custom\nrule that packages its `srcs` as a directory artifact (`TreeArtifact`)\nand compiles a `rust_library` and `rust_test` from it.\n\nI have taken special care in the rustc argument construction to ensure\nit is compatible with the new [bazel path remapping\nguidelines](https://github.com/bazelbuild/bazel/discussions/22658).\n\nWhile here, added a few checks in the rules for combinations of `srcs`,\n`crate` and `crate_root` attributes that don\u0027t make sense and would\ncause compilation to fail later anyways." }, { "commit": "7a7ea1c3b4f2c510d023b6421d18dfb5546e5175", "tree": "bcd36d40462f5009bd4dbd528d14056615bd58dc", "parents": [ "eaad03d4341a878a62fcdb6b31f7bf5f8587177a" ], "author": { "name": "Alex Conrey", "email": "ajcblz2019@gmail.com", "time": "Mon Jul 20 18:34:30 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 20 18:34:30 2026" }, "message": "Reexport output groups for rustfmt and clippy tests (#4158)\n\nThis change updates `rustfmt_test` and `rust_clippy_test` to behave more\nconsistently with the aspect output groups by ensuring transitive\ntargets in the transitioned configuration get added to `//...`\ninvocations." }, { "commit": "eaad03d4341a878a62fcdb6b31f7bf5f8587177a", "tree": "64c504bfdda7cf7905971c5bd3c4711e4d018863", "parents": [ "c49e0bb62cacc9dc3c5f44dc19782dd07aa3eb1a" ], "author": { "name": "Synchronization Acknowledgement", "email": "77421532+sin-ack@users.noreply.github.com", "time": "Mon Jul 20 17:32:06 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 20 17:32:06 2026" }, "message": "Point CARGO_MANIFEST_DIR to transformed sources dir (#4154)\n\nCrates with generated inputs have their source files and compile data\nstaged under bazel-out so rustc can resolve modules from one root. The\ncompile action still points `CARGO_MANIFEST_DIR` at the source package,\nwhich is absent from the sandbox and breaks proc macros that read files\nrelative to the manifest.\n\nAssisted-by: GPT-5.6 Sol" }, { "commit": "c49e0bb62cacc9dc3c5f44dc19782dd07aa3eb1a", "tree": "da9c9ad0c264d8bb279c6a99e8336b28d180719b", "parents": [ "9e9c4eca6c6fb4c44338829a1a473ebba149be0d" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jul 20 08:29:07 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 20 08:29:07 2026" }, "message": "Added Rust 1.97.1 (#4155)\n\nhttps://blog.rust-lang.org/2026/07/16/Rust-1.97.1/" }, { "commit": "9e9c4eca6c6fb4c44338829a1a473ebba149be0d", "tree": "365c2cd7e69b14be8f8ce0d077048dfc9f208e99", "parents": [ "6c5cc322721c5783f853eee6c0c5f708aea14c1e" ], "author": { "name": "Alex Conrey", "email": "ajcblz2019@gmail.com", "time": "Fri Jul 17 19:01:37 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 17 19:01:37 2026" }, "message": "Add lint test rules for transitive targets (#4156)\n\nChanges:\n- Add `rust_clippy_test` for having a test target that runs clippy on a\nlist of targets\n- Add a `transitive` bool to `rustfmt_test` that aggregates\n`rustfmt_aspect` outputs from deps of `targets`. This behavior also\napplies to the new `rust_clippy_test`" }, { "commit": "6c5cc322721c5783f853eee6c0c5f708aea14c1e", "tree": "0ce2f45699a87bd610f06253f5866e674507ddda", "parents": [ "5786455b5c3fc189cb907ef7d29ff3e895d589ed" ], "author": { "name": "Jorge Gorbe Moya", "email": "slack@codemaniacs.com", "time": "Mon Jul 13 08:28:45 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jul 13 08:28:45 2026" }, "message": "Move flags passed in `rust_flags` near the end of the rustc invocation. (#4135)\n\nThis allows callers of rustc_compile_action to override the default\nflags.\n\nThe motivating example for making this change was some path remapping\ndone by Crubit\n(https://github.com/google/crubit/blob/685a46aabbdf6552803c5bd77da6628008d0d245/rs_bindings_from_cc/bazel_support/compile_rust.bzl#L100).\nPR #4106 added another `--remap-path-prefix` flag after the code that\nadds `rust_flags` to the rustc invocation, and the new remapping took\nprecedence." }, { "commit": "5786455b5c3fc189cb907ef7d29ff3e895d589ed", "tree": "a16d5703b690adb29fef0591d8b61285a588e228", "parents": [ "dd6729b94835b851e1ff50722174585d96534e53" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Fri Jul 10 12:51:08 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 10 12:51:08 2026" }, "message": "Added Rust 1.97.0 (#4144)\n\nhttps://blog.rust-lang.org/2026/07/09/Rust-1.97.0/" }, { "commit": "dd6729b94835b851e1ff50722174585d96534e53", "tree": "e29564cc1c1b1c36b64c1ee06bbc61be90a1d4fb", "parents": [ "ed321505851d2cc8a5ace048188ef3ba8f7e8d71" ], "author": { "name": "Alex Conrey", "email": "ajcblz2019@gmail.com", "time": "Fri Jul 10 06:52:37 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 10 06:52:37 2026" }, "message": "Add rust-analyzer clippy end-to-end test (#4147)\n\nImplements https://github.com/bazelbuild/rules_rust/pull/4143 and also\nfixes a memory leak from multiple rust-analyzer processes for different\nrust-analyzer-workspaces.\n\ncloses https://github.com/bazelbuild/rules_rust/pull/4143" }, { "commit": "ed321505851d2cc8a5ace048188ef3ba8f7e8d71", "tree": "32c002ca83f24de564513b85275e10e9b0f1100f", "parents": [ "7cd42b83c0f4d1bbd68376685b425de08fa58d83" ], "author": { "name": "Keith Smiley", "email": "keithbsmiley@gmail.com", "time": "Thu Jul 09 18:26:18 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 09 18:26:18 2026" }, "message": "Return repo_metadata from repository rules (#4146)\n\nThis allows the remote repo contents cache to cache the result of these" }, { "commit": "7cd42b83c0f4d1bbd68376685b425de08fa58d83", "tree": "929dcf723e77f47dbcae9b030ed13d2e9d223d9b", "parents": [ "88ab9d0c3e21fa3f8721cea2875809315930d6fc" ], "author": { "name": "Martin Kuntz Jacobsen", "email": "56176095+TrapsterDK@users.noreply.github.com", "time": "Wed Jul 08 22:18:38 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jul 08 22:18:38 2026" }, "message": "Fix rust-analyzer proc-macro merge for k8-opt-exec paths (#4140)\n\nWritten by AI, reviewed by human.\n\nFixes #4139.\n\n## Summary\n\n`consolidate_crate_specs` prefers proc-macro dylib paths that look like\nexec outputs. The previous marker matched paths with `-opt-exec-`, but\nBazel can also emit exec paths like `bazel-out/k8-opt-exec/bin/...`.\n\nThis updates the marker to match both forms and adds a regression test\nfor the unsuffixed `k8-opt-exec/bin` path shape.\n\n## Testing\n\n```sh\nbazel test --cache_test_results\u003dno //tools/rust_analyzer:gen_rust_project_lib_test\n```" }, { "commit": "88ab9d0c3e21fa3f8721cea2875809315930d6fc", "tree": "d1d5609e9baa57a7625458c822ca416c707842f8", "parents": [ "16d03098f1a4d8b40ed672c8b6650dd274e66282" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Wed Jul 08 21:50:09 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jul 08 21:50:09 2026" }, "message": "Add jsonc support for rust-analyzer setup (#4126)\n\nThe change aims to cleanly handle merging rust-analyzer settings into\nexisting vscode config files that are `jsonc` vs valid `json`." }, { "commit": "16d03098f1a4d8b40ed672c8b6650dd274e66282", "tree": "68788498337417f5af1dd404581ed57638451000", "parents": [ "46d67bc1fda4592dab7465c8152d94ae6f969cfc" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Wed Jul 08 21:45:56 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jul 08 21:45:56 2026" }, "message": "Fix rust-analyzer selecting the wrong proc-macro cfg (#4137)\n\ncloses https://github.com/bazelbuild/rules_rust/issues/4136" }, { "commit": "46d67bc1fda4592dab7465c8152d94ae6f969cfc", "tree": "87eb5b45e13a610f4dac65e96670e40cca09d6a6", "parents": [ "dedf05304354aace6a76ae78030a9d69c74e37d4" ], "author": { "name": "Cameron Mulhern", "email": "csmulhern@gmail.com", "time": "Tue Jul 07 05:43:50 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jul 07 05:43:50 2026" }, "message": "Fixes BEP path handling for rust analyzer specs (#4130)\n\nThe rewrite of the Rust Analyzer auto-discovery pipeline (see #4075)\nintroduced a bug for users who use\n`--experimental_convenience_symlinks\u003dignore` (i.e. have no bazel-out\nsymlink in their workspace).\n\n`parse_output_group_paths` documentation suggests that output paths are\nalways absolute\n\n\nhttps://github.com/bazelbuild/rules_rust/blob/dedf05304354aace6a76ae78030a9d69c74e37d4/tools/rust_analyzer/bep.rs#L107-L110\n\nbut that is not true for BEP events that trigger the fallback\nreconstruction path\n\n\nhttps://github.com/bazelbuild/rules_rust/blob/dedf05304354aace6a76ae78030a9d69c74e37d4/tools/rust_analyzer/bep.rs#L241-L243\n\nThis PR detects those cases and anchors those paths to the execution\nroot, making them also absolute." }, { "commit": "dedf05304354aace6a76ae78030a9d69c74e37d4", "tree": "56dd577aab3d961bed8b1282889d2188aba50c12", "parents": [ "64c826a3741aae38aa27e0c02c4e080aa20f19cb" ], "author": { "name": "Bas van Dijk", "email": "bas@van.dijk.ch", "time": "Sun Jul 05 14:19:22 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sun Jul 05 14:19:22 2026" }, "message": "Fix unresolved `${out_dir}` token in dep env files (#4124)\n\n### The bug\n\nSince the `OUT_DIR` sanitization work (#4050 / #4011, first released in\n0.71.x), `outputs_to_dep_env` redacts the producer\u0027s `out_dir` to the\ngeneric `${out_dir}` substitution token, the same way `outputs_to_env`\ndoes.\n\nThat redaction is only correct for `_bs.env` files, which are consumed\nby the target that directly owns the build script (where\n`process_wrapper`\u0027s `--out-dir` resolves the token to the right\ndirectory). Dep env (`DEP_*`) files, however, are consumed by\n*downstream* crates\u0027 build scripts: their runner only substitutes\n`${pwd}`, and their own `out_dir` points to a different directory. The\ntoken is therefore left unresolved, or would resolve to the wrong\ndirectory.\n\nReal-world failure: `libssh2-sys`\u0027s build script fails to find `zlib.h`\nbecause `libz-sys`\u0027s `DEP_Z_INCLUDE` contains a literal `${out_dir}`\npath component. Found while upgrading `rules_rust` to 0.71.3 in\ndfinity/ic (see dfinity/ic#10632, where this fix is currently carried as\na patch).\n\n### The fix\n\nOnly substitute the exec root in dep env files and keep the real\n`out_dir` path. That path is valid for consumers: the producer\u0027s\n`out_dir` is a declared input of downstream build script actions.\n\n### Tests\n\n* Unit test\n`out_dir_in_dep_env_value_is_not_redacted_to_substitution_token` in\n`cargo/private/cargo_build_script_runner/lib.rs`.\n* End-to-end regression test `//cargo/tests/dep_env:build_read_out_dir`\nmirroring the libz-sys → libssh2-sys scenario: a producer build script\nadvertises `cargo:include\u003d$OUT_DIR/include` and the consumer build\nscript asserts `DEP_Z_INCLUDE` points at an existing directory. Fails\nwithout the fix, passes with it.\n\n---\n\nAssisted-by: GitHub Copilot" }, { "commit": "64c826a3741aae38aa27e0c02c4e080aa20f19cb", "tree": "0192f70fe137af48098d542bfc58624e1b91986b", "parents": [ "bd2a8f01549844fd91a9e5098fabc78c56d55734" ], "author": { "name": "Keegan Carruthers-Smith", "email": "keegan.csmith@gmail.com", "time": "Sun Jul 05 12:39:00 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sun Jul 05 12:39:00 2026" }, "message": "fix: declare rustfmt aspect action toolchain (#4128)\n\nThe --incompatible_auto_exec_groups flag requires Starlark actions to\ndeclare whether their executable/tools come from an action toolchain.\nThis is not a Bazel default today, but it is exposed through strict\npreset configurations and is intended to catch rules that rely on\nimplicit action toolchain inference.\n\nrustfmt_aspect runs rustfmt from rules_rust\u0027s rustfmt toolchain, but the\nformatting action does not declare that action toolchain. Declare the\nmatching rustfmt toolchain so the action\u0027s toolchain behavior is\nexplicit without changing its inputs or execution model." }, { "commit": "bd2a8f01549844fd91a9e5098fabc78c56d55734", "tree": "fe50a3e8e6deca47db7abaa1a1fa2aae11b1cad8", "parents": [ "4c2c46038fd9d794191c5df0865d0e0de059b73d" ], "author": { "name": "Martin Geisler", "email": "martin@geisler.net", "time": "Sun Jul 05 12:21:40 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sun Jul 05 12:21:40 2026" }, "message": "Fix Clippy errors from #4127 (#4129)\n\nThese were not triggered before the PR was merged. I’m not sure why more\ntests are run on `main` than on PRs, but maybe this could be revisited\nto at least gate PRs on this kind of thing?" }, { "commit": "4c2c46038fd9d794191c5df0865d0e0de059b73d", "tree": "7e218e4c2ca7e2aeebb2426ada02f9de2f8c68b4", "parents": [ "7fb3e6d051719d5d4f1d59f6499c40435351e67e" ], "author": { "name": "Martin Geisler", "email": "martin.geisler@proton.ch", "time": "Fri Jul 03 23:25:05 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 03 23:25:05 2026" }, "message": "Tolerate partial build failures during rust-analyzer discovery (#4127)\n\n`discover_bazel_rust_project` builds the rust-analyzer aspect over the\nwhole workspace and bailed on any non-zero Bazel exit. In a large\nmonorepo a single broken target (e.g. an unrelated, unmaintained one)\naborted the build, leaving rust-analyzer with no Bazel project model. It\nthen silently falls back to a Cargo workspace, which breaks proc-macro\nexpansion (toolchain ABI mismatch) and materializes a stray `target/`.\n\nPass `--keep_going` so Bazel keeps building the rest of the graph, and\ntreat the result as usable when the BEP still yielded crate specs:\nproceed with a `log::warn` that the project may be incomplete, and only\nfail when zero specs were produced. This mirrors `flycheck`\u0027s existing\nexit-code handling.\n\nAdd an end-to-end test that stands up a workspace with one good\n`rust_library` and one target that fails analysis, then checks discovery\nstill returns a project containing the good crate. Unit tests cover the\n`assess_discovery` decision.\n\nWritten with Claude, but I believe I understand what is going on." }, { "commit": "7fb3e6d051719d5d4f1d59f6499c40435351e67e", "tree": "b26e2def6f32d68f2688ddc96f0a33f3c69dc051", "parents": [ "256b6b92476204e2b6a0ee2e6659cde0017bafdd" ], "author": { "name": "Jorge Gorbe Moya", "email": "slack@codemaniacs.com", "time": "Fri Jul 03 14:55:05 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jul 03 14:55:05 2026" }, "message": "rustc: add support for split debuginfo (#4092)\n\nThis is #3168 by @durin42, with fixes for some of the pre-merge checks.\n\nThis PR adapts the original change to support path mapping when passing\n`-Zsplit-dwarf-out-dir\u003d\u003cpath\u003e`. In order to do this, it adds to\n`construct_arguments` the option to pass `(format_string, File)` as\nelements in the list form of `rustc_flags`. This PR also adds tests for\nthe new functionality.\n\nThe new changes on top of the original PR were written with assistance\nby Gemini.\n\n---------\n\nCo-authored-by: Augie Fackler \u003caugie@google.com\u003e" }, { "commit": "256b6b92476204e2b6a0ee2e6659cde0017bafdd", "tree": "f1215881fb2158d5d11e9a3a65b9b22f05471e9c", "parents": [ "8f4cba1695aff1bfc1346541abb09ec55bb0f354" ], "author": { "name": "Glenn LeBlanc", "email": "g.leblanc135@gmail.com", "time": "Thu Jul 02 21:33:05 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 21:33:05 2026" }, "message": "fix: prefix pwd for imacros flag (#4116)\n\ntoolchains_llvm\n[now](https://github.com/bazel-contrib/toolchains_llvm/commit/119492322ea93f90870a6c8f9c6438480c0f0524)\nforce-includes a header via `-imacros`, which surfaced this bug." }, { "commit": "8f4cba1695aff1bfc1346541abb09ec55bb0f354", "tree": "93ef75695fff24be25b59ad20933b1f225ba16df", "parents": [ "f7f212ad30a58475d6252a8607cf5cdb5f59bbdd" ], "author": { "name": "Krasimir Georgiev", "email": "krasimir@google.com", "time": "Thu Jul 02 10:32:52 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 10:32:52 2026" }, "message": "add a mnemonic to a cargo dep env action (#4123)" }, { "commit": "f7f212ad30a58475d6252a8607cf5cdb5f59bbdd", "tree": "e415e8b4460efbfd03d70309439833fc0fffd599", "parents": [ "fc45989eb148d7edd6855d0b2d5ae1f7b63f4fff" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jul 02 03:00:56 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 03:00:56 2026" }, "message": "Release 0.71.3 (#4119)" }, { "commit": "fc45989eb148d7edd6855d0b2d5ae1f7b63f4fff", "tree": "65d99ad90159b3a4f964d4f7656accc14d7e0e75", "parents": [ "227dac1b7a8a1b99359d019a3bfe7fe052a02092" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jul 02 02:34:16 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 02:34:16 2026" }, "message": "Add path-mapping test for env location expansion (#4120)\n\nAdds regression testing for\nhttps://github.com/bazelbuild/rules_rust/pull/4117 as well as identifies\nsome cases where there are further incompatibilities (namely uses of\n`rust_test.crate`)." }, { "commit": "227dac1b7a8a1b99359d019a3bfe7fe052a02092", "tree": "95883c9a4af0d35df6dba33e3b498f648996781a", "parents": [ "3e58a1d9ca8a8b4bb1d6cbc1cb0464c4c0a55f67" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jul 02 01:50:01 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 01:50:01 2026" }, "message": "Added Rust 1.96.1 (#4121)\n\nhttps://blog.rust-lang.org/2026/06/30/Rust-1.96.1/" }, { "commit": "3e58a1d9ca8a8b4bb1d6cbc1cb0464c4c0a55f67", "tree": "b5028c4d345371e161761b94317ddf3d2afa5776", "parents": [ "155a8afc139f7381e6eedbc9b831e04e99f52c52" ], "author": { "name": "Xiao Yu", "email": "airtrick@gmail.com", "time": "Thu Jul 02 01:10:33 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 01:10:33 2026" }, "message": "Disable path mapping when rustc_env has location expansions (#4117)\n\nLocation expansion happens outside the control of path mapping logic and\nwould produce paths with build configuration in them, breaking path\nmapping\u0027s logic of replacing all build configuration with the literal\n\"cfg\"." }, { "commit": "155a8afc139f7381e6eedbc9b831e04e99f52c52", "tree": "bc325a1ae3860729dcb12fc6d41c305dfaf54437", "parents": [ "08d7cc67ab0d891632a8fb1ae472047096119679" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jul 02 01:09:11 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jul 02 01:09:11 2026" }, "message": "Add cross-platform compatible launcher for rust-analyzer (#4118)\n\nFor vscode users who commit `.code-workspace` or `settings.json`, this\nchange introduces a cross-platform compatible entrypoint for\nrust-analyzer infrastructure. Note that this doesn\u0027t mean the binaries\nare magically platform agnostic. It just means the two files mentioned\nwill be compatible on both Unix and Windows platforms if the vscode\nconfig files are source controlled." }, { "commit": "08d7cc67ab0d891632a8fb1ae472047096119679", "tree": "4f9a966f9b4ed412d732078484b86e9b92360f20", "parents": [ "aa5da6531178f585ef4426c3ba6c061cb451198e" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Sun Jun 28 01:03:56 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sun Jun 28 01:03:56 2026" }, "message": "Release 0.71.2 (#4115)" }, { "commit": "aa5da6531178f585ef4426c3ba6c061cb451198e", "tree": "92dbc6204ed200140c6cfa082e660c62bd576ed5", "parents": [ "ab2ba8403255de436f4506cd839858ef77b5ac0b" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Sun Jun 28 00:42:45 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sun Jun 28 00:42:45 2026" }, "message": "Avoid reliance on bazel-bin for rust-analyzer IDE setup (#4112)\n\nThis change removes any reliance `setup` placed on `bazel-bin` as it\u0027s\nan unreliable path. Instead binaries like `flycheck` are installed into\nthe setup directory and the output_base is used to identify\nrust-analyzer and the sysroot." }, { "commit": "ab2ba8403255de436f4506cd839858ef77b5ac0b", "tree": "23bc9f288473557b479e6d6a0752fa943e5da92b", "parents": [ "dc6c891dd5adc4631e7315d522ee4b870e5bf77c" ], "author": { "name": "Régis Desgroppes", "email": "rdesgroppes@gmail.com", "time": "Sat Jun 27 17:37:02 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sat Jun 27 17:37:02 2026" }, "message": "Restore `crate_universe/extension.bzl` shim with a deprecation warning (#4114)\n\n#4005 removed `crate_universe/extension.bzl`, the deprecated re-export\nof `crate_universe/extensions.bzl`, as part of dropping WORKSPACE\nsupport.\n\nDownstream projects may still load `crate` from that path via\n`use_extension`, so any build that resolves `rules_rust` 0.71.0 with\nsuch a module in its graph fails.\n`protobuf` 35.1, the newest release on BCR, is one such module.\n\nRestore the shim and print a deprecation warning at load time, giving\ndownstream modules a short window to migrate to `extensions.bzl`, e.g.:\n- protocolbuffers/protobuf#28226.\n\nCloses #4111." }, { "commit": "dc6c891dd5adc4631e7315d522ee4b870e5bf77c", "tree": "d40b3156432936d58f0d21a64af5f86ec77fc25d", "parents": [ "2f69054614bbe022492f9121bdf1475dfdb14bd6" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Fri Jun 26 15:29:52 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jun 26 15:29:52 2026" }, "message": "Fix publish-to-bcr author (#4108)\n\nA random user was used on\nhttps://github.com/bazelbuild/bazel-central-registry/pull/9424, this\nchange fixes that and aligns with the info provided from\nhttps://api.github.com/users/bazel-io" }, { "commit": "2f69054614bbe022492f9121bdf1475dfdb14bd6", "tree": "e1252b19f3f6b53efdac2548756aef39387ff598", "parents": [ "cdd9b2778fe396079a6cb4cc7e1b5a376b60dbd6" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Fri Jun 26 15:19:44 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jun 26 15:19:44 2026" }, "message": "Add `link_deps` crate_universe annotation (#4109)\n\nhttps://github.com/bazelbuild/rules_rust/pull/4024 now adds noisy prints\nthat users have no way to handle when using crate_universe. This change\nadds annotations so the prints can be actioned." }, { "commit": "cdd9b2778fe396079a6cb4cc7e1b5a376b60dbd6", "tree": "e35b0803de0c10dc80a45d89a15f43fdd7af2f4f", "parents": [ "4fee5935ba71773f6d6ef67e05e6e5c54a078e1d" ], "author": { "name": "Keith Smiley", "email": "keithbsmiley@gmail.com", "time": "Thu Jun 25 22:17:48 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 22:17:48 2026" }, "message": "Fix releases (#4107)\n\nCo-authored-by: UebelAndre \u003cgithub@uebelandre.com\u003e" }, { "commit": "4fee5935ba71773f6d6ef67e05e6e5c54a078e1d", "tree": "58f9f3e9fc2ff7532dcf177d323ace8d101eb9ea", "parents": [ "f9c09637a0aeff457ce4bb757f007fc674e67d14" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 25 21:09:33 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 21:09:33 2026" }, "message": "Release 0.71.0 (#4082)" }, { "commit": "f9c09637a0aeff457ce4bb757f007fc674e67d14", "tree": "a8796d70687abd9b5b1217ae6aab9983ca737de9", "parents": [ "2f83a8fd637e584ae3ea61f97d369bfdb907d192" ], "author": { "name": "Erik Gilling", "email": "konkers@google.com", "time": "Thu Jun 25 20:59:37 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 20:59:37 2026" }, "message": "Fix bindgen flag merging between clang_flags and cc_common (#4100)\n\nIf a param flag (a flag with a following argument like -isystem) exists\nboth in the flags returned by\n`cc_common.get_memory_inefficient_command_line` and a\n`rust_bindgen_library`\u0027s `clang_flags`, the secondary argument of the\nflag from `cc_common` was getting dropped." }, { "commit": "2f83a8fd637e584ae3ea61f97d369bfdb907d192", "tree": "27dfe26b420101e38c7c7c9b0cf0e89201ef7ecc", "parents": [ "eda8f0292e28881ff927557fc169aaba3ef8c210" ], "author": { "name": "Keith Smiley", "email": "keithbsmiley@gmail.com", "time": "Thu Jun 25 20:52:42 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 20:52:42 2026" }, "message": "Add more sysroot flags that require prefixing (#4101)" }, { "commit": "eda8f0292e28881ff927557fc169aaba3ef8c210", "tree": "e8872d57a1fec91b77e721a6d775cf8b3b8016f6", "parents": [ "99ad03eb9ac0e11489f2dbd73af1e13b69f19401" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 25 20:19:56 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 20:19:56 2026" }, "message": "Make setup authorative over rust-analyzer paths (#4105)\n\nThis change adds control over the launchers and cache dir through the\nrust-analyzer setup tool so users don\u0027t see mystery files appear in\ntheir checkout when they don\u0027t want." }, { "commit": "99ad03eb9ac0e11489f2dbd73af1e13b69f19401", "tree": "a15408521df93ec6c7e98baf0c81a5a9642b69bd", "parents": [ "c55282e3b872157a0354b8bb62d6bcec25e4163c" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 25 20:08:30 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 20:08:30 2026" }, "message": "Render crates into subpackages (#4093)\n\nCurrently `crate_universe` renders aliases into a single package for\ndevelopers to consume. The issue with this design is that for projects\nwith massive amounts of dependencies, Bazel parsing that BUILD file can\nbe slow and have noticable impacts on analysis. This change updates\n`crate_universe` to render aliases into sub-packages instead of a root\nBUILD file in the repo hubs. In practice this means dependencies that\nwere once accessed via `@crate_index//:clap` are now accessed via\n`@crate_index//clap`. Currently both root level aliases are still\nrendered but can be disabled via the new\n`incompatible_no_root_alias_targets` flag." }, { "commit": "c55282e3b872157a0354b8bb62d6bcec25e4163c", "tree": "a966a28c2c655b76b5fec16aa632bfdbd33ca4cc", "parents": [ "b62b2811cc88e5bce4d1195ac223f054e8d8a4b6" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 25 19:54:14 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 19:54:14 2026" }, "message": "Add ibazel support to mdbook_server (#4068)\n\nThis change adds [ibazel](https://github.com/bazelbuild/bazel-watcher)\nsupport to the `mdbook` server." }, { "commit": "b62b2811cc88e5bce4d1195ac223f054e8d8a4b6", "tree": "52668fca7a66070f3fb2424e5ad8265489e484d4", "parents": [ "39a22fe1532ceea086b528f2f7ce5a0dad846e96" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 25 19:10:38 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 25 19:10:38 2026" }, "message": "Fix coverage for crates with mixed sources (#4106)\n\nAn expansion of https://github.com/bazelbuild/rules_rust/pull/4079 with\nsome added testing.\n\ncloses https://github.com/bazelbuild/rules_rust/pull/4079" }, { "commit": "39a22fe1532ceea086b528f2f7ce5a0dad846e96", "tree": "c13936fbf8c2eb5cc70034bfe823315489349a10", "parents": [ "3a95857e86144b130749ded8e25179951e640a65" ], "author": { "name": "Krasimir Georgiev", "email": "krasimir@google.com", "time": "Wed Jun 24 13:27:47 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jun 24 13:27:47 2026" }, "message": "remove mention of cc_deps from warning message (#4099)\n\nA follow-up from https://github.com/bazelbuild/rules_rust/pull/4024\nwhere we inadvertently mentioned a feature that doesn\u0027t exist." }, { "commit": "3a95857e86144b130749ded8e25179951e640a65", "tree": "9c7bf1bcf5a3b8f7ed994a500865b7441e7c95fa", "parents": [ "1ce5fb365e3394a04b28232adf8b0ebb24305f6e" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Tue Jun 23 22:26:10 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jun 23 22:26:10 2026" }, "message": "Consolidate crate_universe generated `defs.bzl` into `crates.bzl` (#4094)\n\nThis change begins to consolidate `defs.bzl` into `crates.bzl` so users\ndon\u0027t get confused as to which of the two to use. In doing so, I have\nalso consolidated the repository rules for where crate aliases are\ngenerated between the `crate` module extension and outputs to\n`crates_vendor` rule as a cleanup and consolidation effort. In the\nfuture I plan to have that rule be responsible for aliases and the crate\ndependency interface." }, { "commit": "1ce5fb365e3394a04b28232adf8b0ebb24305f6e", "tree": "a302f88fc0a75f18690f9fbcc55517af4a93c1f1", "parents": [ "20b9cf99be9c178e76588c2f1f6f2b0bb54849ab" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Tue Jun 23 22:26:02 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jun 23 22:26:02 2026" }, "message": "Add `discoverConfig` Support for rust-analyzer (#4075)\n\nThis change improves rust-analyzer support by moving away from\n`rust-project.json` and promoting a more automated approach.\nDocumentation has been updated to reflect the recommended integration.\n\nChanges:\n- Implement Build-Event-Service parsing to avoid globbing for bazel\noutputs.\n- Implements new `setup` tool that users can invoke to configure their\nIDE for Bazel-backed rust-analyzer support.\n\ncloses https://github.com/bazelbuild/rules_rust/issues/2488\ncloses https://github.com/bazelbuild/rules_rust/issues/3762" }, { "commit": "20b9cf99be9c178e76588c2f1f6f2b0bb54849ab", "tree": "5e453dea7cda0a5ec45e5676873df02612d5db20", "parents": [ "a9cec9ae8816790d39e37aa496992eb5ba2ced36" ], "author": { "name": "Paul Draper", "email": "paulddraper@gmail.com", "time": "Tue Jun 23 15:52:17 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jun 23 15:52:17 2026" }, "message": "Suppress noisy build script warnings (#4046)\n\nFixes #3880.\n\n`cargo::warning\u003d` lines from `build.rs` are forwarded to stderr\nunconditionally, which is noisy for `-sys` crates such as `zstd-sys`,\n`aws-lc-sys`, `openssl-sys`. Under Cargo these warnings are hidden for\nregistry/git deps unless the build fails or the user passes `-vv`; under\nrules_rust the user always sees them.\n\nThis PR adds two complementary fixes (both discussed on the issue):\n\n1. **Global flag**\n`--@rules_rust//cargo/settings:emit_build_script_warnings` (default\n`auto`). Values:\n- `on` — emit for every target, overriding any per-target opt-out\n(useful for debugging an `-sys` crate).\n- `auto` — respect the per-target `emit_warnings` attribute.\n`crate_universe`-generated targets opt out, so registry crates stay\nquiet (matching Cargo); first-party targets emit by default.\n - `off` — silence build-wide.\n2. **Per-target attribute** `cargo_build_script(emit_warnings \u003d ...)`\n(default `True`). `crate_universe` renders generated\n`cargo_build_script` targets with `emit_warnings \u003d False`. Honored only\nwhen the global flag is `auto`.\n\n---------\n\nCo-authored-by: UebelAndre \u003cgithub@uebelandre.com\u003e" }, { "commit": "a9cec9ae8816790d39e37aa496992eb5ba2ced36", "tree": "1de9fbcd4f44e56a5493e720d7fbaaebefc3bbd5", "parents": [ "fb01b69e20a613d3b37a91662f25a73faecfb4f8" ], "author": { "name": "Alex Trotta", "email": "44127594+Ahajha@users.noreply.github.com", "time": "Tue Jun 23 14:40:28 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jun 23 14:40:28 2026" }, "message": "Remove C Python headers from pyo3 build actions (#4095)\n\nhttps://github.com/bazelbuild/rules_rust/pull/4024 introduced a warning\nfor targets adding CC deps in `deps`. The warning calls out putting this\nin `link_deps` or `cc_deps`. The latter makes more sense here... but\ndoesn\u0027t actually exist. However, I don\u0027t think this matters anyways, as\nI don\u0027t think it\u0027s needed (this works with an internal codebase)." }, { "commit": "fb01b69e20a613d3b37a91662f25a73faecfb4f8", "tree": "afbee0cfbaea96f7302e0150173cd03a46b340eb", "parents": [ "a2113e94b524e468ea16b7b89bd2c6e26e4f0f88" ], "author": { "name": "Paul Salaberria", "email": "psalaberria002@gmail.com", "time": "Mon Jun 22 10:37:24 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 22 10:37:24 2026" }, "message": "fix(cargo_build_script): expand ${pwd} for execpaths and locations in build_script_env (#4088)\n\nSingular `$(execpath ...)` and `$(location ...)` were already prefixed\nwith `${pwd}/` so build_script_runner could resolve them to absolute\npaths at run time. The plural forms `$(execpaths ...)` and `$(locations\n...)` were silently omitted from this handling, leaving their paths as\nexecroot-relative.\n\nFor plural forms each macro is expanded individually (via\nctx.expand_location) and every resulting space-separated path is\nprefixed with `${pwd}/`." }, { "commit": "a2113e94b524e468ea16b7b89bd2c6e26e4f0f88", "tree": "08ef2efad798b21a078661b7b95f8c9ee1b488cd", "parents": [ "dad9720297c943d944877fd9a143f57c83ed59a0" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 18 13:34:28 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 18 13:34:28 2026" }, "message": "Move rust/toolchain.bzl implementation into rust/private (#4087)\n\nThis change is a noop for our public interface but allows for more\nhelper functions to exist in `toolchains.bzl` without them expanding the\npublic interface." }, { "commit": "dad9720297c943d944877fd9a143f57c83ed59a0", "tree": "bdd0ece2fc99e278556914f3c16bd651dcf62f8b", "parents": [ "6a3e2f934fa209d7827738b2f1d4f46b34dc0db4" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Wed Jun 17 14:03:11 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jun 17 14:03:11 2026" }, "message": "Resolve `\u003cbinary\u003e.runfiles_manifest` from argv[0] in `Runfiles::create()` (#4086)\n\nI have reviewed the runfiles implementation for\n[rules_cc](https://github.com/bazelbuild/rules_cc/tree/f65555ccb4257d65e0a5379f9f476dd748203d4b/cc/runfiles),\n[rules_shell](https://github.com/bazel-contrib/rules_shell/tree/b0fe38e8211df2f05979410a215520eb9eaa9da3/shell/runfiles),\n[rules_go](https://github.com/bazel-contrib/rules_go/tree/370a75048291a6e03fd29bb96f20ecefac5416ad/go/runfiles),\nand\n[rules_python](https://github.com/bazel-contrib/rules_python/tree/99d0c3d187209a4d143790e6d4b706f15b2b294b/python/runfiles)\nto figure out the behavior of runfiles relative to the current binary.\nUnfortunately\n[`current_exe`](https://doc.rust-lang.org/std/env/fn.current_exe.html)\ncanonicalizes the path on some platforms so we need to instead focus on\n`argv[0]` as a more reliable path." }, { "commit": "6a3e2f934fa209d7827738b2f1d4f46b34dc0db4", "tree": "940e87dc6e63ba823b02d2cade98440c4bc9c571", "parents": [ "2a9037e9b702cab7993380a3cc4fb6fb92e49eef" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jun 15 21:13:31 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 15 21:13:31 2026" }, "message": "Fix failing test in rolling bazel version (#4076)\n\nMy assumption is that the hashing algorithm changed in some way in the\nrolling Bazel version. I don\u0027t think we need to test the exact value,\njust that it\u0027s a numeric hash." }, { "commit": "2a9037e9b702cab7993380a3cc4fb6fb92e49eef", "tree": "df198d94cfb03161a06ca134acf321982ff15848", "parents": [ "161ce08d3f589c2ce65d004354a524ee332dbf67" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jun 15 21:13:22 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 15 21:13:22 2026" }, "message": "Add attestation support to releases (#4077)" }, { "commit": "161ce08d3f589c2ce65d004354a524ee332dbf67", "tree": "9630d617aa3cb76bc99fc586eb7f6df58867bc19", "parents": [ "5932417b5c66287fa435c3c65d7df2d4c53fd4da" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jun 15 21:09:46 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 15 21:09:46 2026" }, "message": "Update label_injections to work transitively (#4081)\n\nRendering canonical labels into lockfiles is sensitive to consumers\npotentially having overrides. Instead, injections are applied on the\nfly." }, { "commit": "5932417b5c66287fa435c3c65d7df2d4c53fd4da", "tree": "1e07e824facf4c13d03d3c1ce6a306d4d41e2359", "parents": [ "97e0d25539a1f7aca65625762679fa742ae8d750" ], "author": { "name": "Vipul Gupta", "email": "73114964+1vipulgupta@users.noreply.github.com", "time": "Mon Jun 15 13:58:20 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 15 13:58:20 2026" }, "message": "Added support for rustc self-profiling (#4073)\n\nIntroduced a new build setting,\n`--//rust/settings:zself_profile_events`, to enable rustc\u0027s\n`-Zself-profile` and `-Zself-profile-events` flag. Rust `nightly`\ntoolchain is required for using this feature.\nThe setting accepts patterns to match against crate labels or execution\npaths, allowing fine-grained control over which crates are profiled.\nProfiling data is output to a `\u003ccrate_name\u003e_self-profile` directory.\n\nCo-authored-by: Vipul Gupta \u003civip@google.com\u003e" }, { "commit": "97e0d25539a1f7aca65625762679fa742ae8d750", "tree": "605ebb41e0af8d5b3c980e5bb78aa0be436f717e", "parents": [ "71bdd246a408bfbf1663278cb2e404f5341161fc" ], "author": { "name": "Kohei Watanabe", "email": "mypmc@vec.jp", "time": "Sun Jun 14 18:22:02 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Sun Jun 14 18:22:02 2026" }, "message": "Update pyo3 to 0.29.0 (#4085)\n\nTo support doc comments generation, pyo3 0.28.2\ndoes not include Rust doc comments in generated\n.pyi stubs.\n\nThe patch that rules_rust_pyo3 applied to pyo3 0.28.2\nis not needed for now: PyO3/pyo3#5862 removed\n`resolve_cross_compile_config_path`.\nThe cross-build-script file dependency that caused the\nsandbox path issue no longer exists.\n\n- https://github.com/PyO3/pyo3/issues/4579" }, { "commit": "71bdd246a408bfbf1663278cb2e404f5341161fc", "tree": "2057fe97496228c5fdf05f0ccb072de04e97978f", "parents": [ "0d36c003122dbe617e86f4788390a319f9d7ac58" ], "author": { "name": "Damian Banki", "email": "ddaniel.banki@gmail.com", "time": "Fri Jun 12 09:16:14 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri Jun 12 09:16:14 2026" }, "message": "Support path mapping in Rust Starlark actions (#4063)\n\nTransition from passing raw string paths (`.path`) to passing `File`\nobjects directly to action arguments (`Args`). This allows Bazel to\nmutate paths during execution, which is required for path mapping\ncompatibility.\n\nFor more details on path mapping best practices, see:\nhttps://github.com/bazelbuild/bazel/discussions/22658\n\nCo-authored-by: Krasimir Georgiev \u003ckrasimir@google.com\u003e" }, { "commit": "0d36c003122dbe617e86f4788390a319f9d7ac58", "tree": "d8114c79c6f50d2edd8b0f6b16bbbeea5fa96014", "parents": [ "57d165f38f6b9e3cf14037e19279eadbcf93fee5" ], "author": { "name": "Patrick Scott", "email": "patrick@pmscott.com", "time": "Thu Jun 11 20:04:03 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 11 20:04:03 2026" }, "message": "Fix rust_doc_test linking with native libraries (#4080)\n\nrust_doc_test does not propagate native libraries into the final test\ncommand. This appears to only affect native libraries built by bazel\nrather than ones linked into crates by build.rs. This change only works\nwith static libraries - dynamic libraries are much more complex.\n\nFor example, using the jemalloc bazel module in tikv-jemalloc-sys.\n\n* Add -Clink-arg for all transitive non-crates\n* Add include_linker_inputs to collect all linker inputs\n* Collect linker roots from all libraries and additional inputs" }, { "commit": "57d165f38f6b9e3cf14037e19279eadbcf93fee5", "tree": "1751419c53147a3536443657eb51ba4a6a862fd2", "parents": [ "34ea9343a4acf22481bed84dfbbb232b75f35395" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 11 13:11:48 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 11 13:11:48 2026" }, "message": "Add support for build script runfiles (#4066)\n\nThis change restores support for runfiles in\n`cargo_build_script.script`. There exists one limitation where only\n`cargo_build_script.tools` can be located via runfiles. Any\n`cargo_build_script.data` files should be located relative to the\n`CARGO_MANIFEST_DIR` env var. This is required as there is no existing\ninterface for merging exec (tools) and target (data) runfiles.\n\ncloses https://github.com/bazelbuild/rules_rust/pull/4064" }, { "commit": "34ea9343a4acf22481bed84dfbbb232b75f35395", "tree": "9a0d3b08ec77416a377be0d66a0cc5393a22bcc7", "parents": [ "301d4258fe04566ec641ecc20c6975a52482d725" ], "author": { "name": "Martin Altenburg", "email": "2737351+martin4861@users.noreply.github.com", "time": "Wed Jun 10 15:51:05 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jun 10 15:51:05 2026" }, "message": "Prefix execroot-relative file arguments with pwd (#4067)\n\nPrefix execroot-relative bare positional file args with pwd in cargo\nbuild scripts. This is already done for `-L`, `-isystem`, `--sysroot`,\netc but not for bare positional arguments like\n`bazel-out/bin/compiler-rt/libclang_rt.builtins.static.a`.\n\nThis problem arised when compiling `aws-lc-sys` with\n[hermetic-llvm](https://github.com/hermeticbuild/hermetic-llvm), see\nhttps://github.com/hermeticbuild/hermetic-llvm/issues/405\n\nA minimal working example to reproduce is created in\nhttps://github.com/martin4861/mwe-bootstrapped-rust-clang_rt.builtins.static:\n```\nclang: error: no such file or directory:\n\u0027bazel-out/darwin_arm64-fastbuild-ST-bdec89fd5d65/bin/external/llvm++llvm_source+compiler-rt/clang_rt.builtins.static_/libclang_rt.builtins.static.a\u0027\n```" }, { "commit": "301d4258fe04566ec641ecc20c6975a52482d725", "tree": "e4f05339f8e0b17a580dfd855bd061440b830301", "parents": [ "247703a12bcb8bfb0f9551ead198654cfe953dba" ], "author": { "name": "Cameron Mulhern", "email": "csmulhern@gmail.com", "time": "Wed Jun 10 13:35:35 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jun 10 13:35:35 2026" }, "message": "Fixes rust-analyzer include_dirs for crates with generated sources (#3840)\n\nWhen a crate contains generated sources, `include_dirs` needs to include\nBOTH the root_module directory, and the generated sources directory.\n\nWhen `include_dirs` is empty, the inclusion of the root_module directory\nis done automatically, but when setting `include_dirs`, this needs to be\ndone manually.\n\nSee:\n\nhttps://github.com/rust-lang/rust-analyzer/blob/a84d92ff213e30fb00d7b812e07c4f67e99dcd29/crates/project-model/src/project_json.rs#L123-L131" }, { "commit": "247703a12bcb8bfb0f9551ead198654cfe953dba", "tree": "fc41bf80a396ef6038a7606fbd0e65d9f8c4c6a9", "parents": [ "c4d6c51d8b000c3f349f733da179d70907cb037b" ], "author": { "name": "Vaibhav", "email": "vaibhavshukla@google.com", "time": "Wed Jun 10 09:30:20 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed Jun 10 09:30:20 2026" }, "message": "Add extensions_bindgen_ios task in CI to verify iOS cross-compilation (#4071)\n\nBindgen is failing to generate bindings for the iOS platform in google3\ndue to extra Apple-specific Clang flags that are not currently\nallowlisted by the bindgen implementation.\n\nAdding the iOS task to the upstream CI will help catch any\ncross-compilation failures early." }, { "commit": "c4d6c51d8b000c3f349f733da179d70907cb037b", "tree": "5f4f681c9365d75e4747600492b9a0a3854a0f79", "parents": [ "bf89fb67113ea7a2cb7d9a776a79f8ab6135e9b1" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 04 20:25:38 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 04 20:25:38 2026" }, "message": "Added `label_injection` to crate_universe annotations (#3755)\n\nThe new `label_injection` attribute is used to sanitize \"apparent\nlabels\" used in annotations to \"canonical labels\". A common example of\nthis is when adding external dependencies to `cargo_build_script`\ntargets. E.g.\n\n```starlark\nbazel_dep(name \u003d \"openssl\", version \u003d \"3.3.1\")\n\ncrate \u003d use_extension(\"@rules_rust//crate_universe:extensions.bzl\", \"crate\")\ncrate.annotation(\n crate \u003d \"openssl-sys\",\n build_script_data \u003d [\n \"@openssl//:openssl\",\n ],\n build_script_env \u003d {\n \"OPENSSL_BIN\": \"$(execpath @openssl//:openssl)\",\n },\n label_injection \u003d {\n \"@openssl//:openssl\": \"@openssl//:openssl\",\n },\n)\ncrate.from_cargo(\n name \u003d \"crates_index\",\n cargo_lockfile \u003d \"//:Cargo.lock\",\n manifests \u003d [\"//:Cargo.toml\"],\n)\nuse_repo(crate, \"crates_index\")\n```\n\nBefore this change\n[inject_repo](https://bazel.build/rules/lib/globals/module#inject_repo)\nwould have been needed to get `@openssl` to resolve in the generated\n`openssl-sys` crate. After this, labels are remapped after resolving the\ncanonical label based on the `label_injection` attribute so that even if\nthe module above is consumed as a transitive dependency, the modules are\nstill usable (because `inject_repo` is only applied to the root module)." }, { "commit": "bf89fb67113ea7a2cb7d9a776a79f8ab6135e9b1", "tree": "2ccaca047a02ae264edeec2fb555e8698572fefa", "parents": [ "129a7c9fcade34297e0d17ab7e3386e2eb518437" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 04 18:38:22 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 04 18:38:22 2026" }, "message": "Update crate_universe boringssl with openssl (#4048)\n\nThe openssl example will be far more common than boringssl." }, { "commit": "129a7c9fcade34297e0d17ab7e3386e2eb518437", "tree": "755df0567ab7c4e6ea06c1b9f75ed550b16f0106", "parents": [ "51c5e0f49ee9ec53dcbeab8a49dad29e2e561c1b" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 04 18:11:50 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 04 18:11:50 2026" }, "message": "Statically link crate_universe for MSVC (#4031)\n\ncloses https://github.com/bazelbuild/rules_rust/issues/3833" }, { "commit": "51c5e0f49ee9ec53dcbeab8a49dad29e2e561c1b", "tree": "3d3cbae1379298fb3124d7f6c20609f414be42f8", "parents": [ "30c0f73f026e8b2536dd509d097aab407bbbf1fc" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 04 18:10:28 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 04 18:10:28 2026" }, "message": "Rename using_cxx test to ext_annotations (#4041)\n\nThe test isn\u0027t actually about using\n[cxx](https://github.com/dtolnay/cxx) but instead showing consumption of\ncrate defined annotations. E.g.\n[@cxx//:Cargo.toml#L66-L82](https://github.com/dtolnay/cxx/blob/0cbbf15ec43439e51b99d895e1f72162de81cd30/Cargo.toml#L66-L82)" }, { "commit": "30c0f73f026e8b2536dd509d097aab407bbbf1fc", "tree": "6cb14e6c6dadc8f46e36ad0b5e18d6645c16f812", "parents": [ "59a507e343825ddc5a0478ef3b063ae199d4d1a1" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu Jun 04 12:43:43 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu Jun 04 12:43:43 2026" }, "message": "Fix bindgen C++17 transition on Windows (#4069)\n\nThis is more correct for all rules_cc available compilers." }, { "commit": "59a507e343825ddc5a0478ef3b063ae199d4d1a1", "tree": "3a45355f88717089af6d15eb448ce1baa6adb45d", "parents": [ "6910b34e8096fe37ea0d6f1d2e8fd99467ac3660" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Tue Jun 02 13:29:19 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jun 02 13:29:19 2026" }, "message": "Split rustdoc test compilation and execution (#4034)\n\nThis change introduces a new `RustdocTestCompile` action which takes\nadvantage of the nightly rustc flag `-Zunstable-options\n--persist-doctests` to have rustdoc tests written to disk to be executed\nin a separate action, similar to a normal `rust_test` which first\ncompiles the test and then executes it in a test action.\n\nTo use this change a nightly toolchain is required and the use of\n`--@rules_rust//rust/settings:experimental_compile_rustdoc_tests\u003dTrue`.\n\ncloses https://github.com/bazelbuild/rules_rust/issues/1431" }, { "commit": "6910b34e8096fe37ea0d6f1d2e8fd99467ac3660", "tree": "0a18bef8159393080fb528657cd44f0587ee525e", "parents": [ "fabd0f9a32bc0cfb4e0ff7ad14e5525127aa813e" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Tue Jun 02 06:08:29 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue Jun 02 06:08:29 2026" }, "message": "Consume cc deps with PIC when rustc emits PIE binaries (#4062)\n\nToday, rules_rust picks the PIC vs non-PIC variant of cc_library deps\nbased only on the C++ toolchain, feature config, crate type, and\ncompilation mode. But when rustc itself decides to emit a\nPosition-Independent Executable (PIE) for a given target, the Rust\nobjects need PIC-compatible cc deps - otherwise you get link errors from\nmixing PIE Rust objects with non-PIC C/C++ objects (the failure mode\ndemonstrated by the existing test from commit\nhttps://github.com/bazelbuild/rules_rust/commit/70f8fb7814d1b2af7f2cb0c4bdfeebf3e2e47ff4\n\"Make native_deps test fail with pie\").\n\nThis PR teaches Bazel when rustc will pass `-pie` to the linker by\nporting rustc\u0027s per-target `position_independent_executables` truth\ntable into Starlark, then feeding that into the PIC selection.\n\nRelates to #118" }, { "commit": "fabd0f9a32bc0cfb4e0ff7ad14e5525127aa813e", "tree": "e04bf8320cc5f1fc70f12dc7706c9f62480b1ee5", "parents": [ "20dbf36a3424b8b6793d26c5ab518c37367c06c5" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jun 01 23:27:11 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 01 23:27:11 2026" }, "message": "Expose `opt_level` in `rust` extension (#4061)" }, { "commit": "20dbf36a3424b8b6793d26c5ab518c37367c06c5", "tree": "f657723d8d5666830cbf0e0af662e4b65fb6bf61", "parents": [ "0dc66fa8f47f102f49a27f1328d740081e3b6995" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Mon Jun 01 13:48:57 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 01 13:48:57 2026" }, "message": "Added Rust 1.96.0 (#4060)\n\nhttps://blog.rust-lang.org/2026/05/28/Rust-1.96.0/" }, { "commit": "0dc66fa8f47f102f49a27f1328d740081e3b6995", "tree": "ba0e2b8b7f67d89a12d1a5b8a593876325bf8169", "parents": [ "e13543d59dd19ca75ebb3f5f1015a167e0c9f2a2" ], "author": { "name": "Suyash Agarwal", "email": "71758361+Suyashagarw@users.noreply.github.com", "time": "Mon Jun 01 12:33:44 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 01 12:33:44 2026" }, "message": "feature: introduce link_deps attribute for native library linkage (#4024)\n\nThis change adds a dedicated link_deps attribute to Rust rules, allowing\nnative symbols to be linked without exposing them as Rust crates.\n\nCloses #4023 \n\nKey changes:\n* Added link_deps to _COMMON_ATTRS for CcInfo/CrateInfo targets.\n* Filtered link_deps out of rust_proc_macro to avoid transition\ncomplexity.\n* Implemented transform_link_deps to extract linkage context while\nhiding crate metadata.\n* Updated _assert_correct_dep_mapping to print a proactive warning for\nnative libraries listed in deps.\n* Added unit tests in test/unit/link_deps to verify correct linkage and\nprovider propagation.\n\nThis provides a cleaner separation of concerns between Rust modules and\nnative code linkage while maintaining full backward compatibility for\nexisting targets." }, { "commit": "e13543d59dd19ca75ebb3f5f1015a167e0c9f2a2", "tree": "b5432a27eba4979eb5aa3d57856d9cdf8737882f", "parents": [ "e0ddf88bfa1edc22549134ff13d3aefa80994794" ], "author": { "name": "Jorge Gorbe Moya", "email": "slack@codemaniacs.com", "time": "Mon Jun 01 09:43:02 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Mon Jun 01 09:43:02 2026" }, "message": "Support `--incompatible_exclude_starlark_flags_from_exec_config`. (#4056)\n\nThis change adds `scope \u003d \"universal\"` to some settings that need to be\npreserved in exec config." }, { "commit": "e0ddf88bfa1edc22549134ff13d3aefa80994794", "tree": "c8b07a068c457c3b389e2e00ce1b0b137d61b020", "parents": [ "179d109ef8151a256653c47beb27f817ba968d41" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu May 28 17:24:01 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu May 28 17:24:01 2026" }, "message": "Fix incorrect exec transition for cargo_build_script (#4040)\n\nRelying on an exec configuration through targets consumed in `target`\nleads to the potential for `cfg \u003d \"exec\"` to be evaluated differently in\nthe transitive target (in this case,\n`cargo_build_script_runfiles.script`) and the consumer\n(`cargo_build_script.data_runfiles`). This change moves the script\ndirectly back to `cargo_build_script` in `cfg \u003d \"exec\"` and separately\nuses a `cfg \u003d \"target\"` intermediate rule to implement runfiles (solving\nfor https://github.com/bazelbuild/bazel/issues/15486).\n\ncloses https://github.com/bazelbuild/rules_rust/issues/3201\nhttps://github.com/bazelbuild/rules_rust/issues/3893" }, { "commit": "179d109ef8151a256653c47beb27f817ba968d41", "tree": "87f30bf496a7214b231323a5eeed1afebfe38a85", "parents": [ "0eca14919146d12010da680eb3c19c777dd09a4f" ], "author": { "name": "scentini", "email": "rosica@google.com", "time": "Thu May 28 17:14:46 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu May 28 17:14:46 2026" }, "message": "Update CONTRIBUTING.md (#4051)\n\nUpdate `CONTRIBUTING.md` to add guidelines around LLM contributions,\npublic interface changes, and manage expectations for contributions to\nareas that are not properly owned/maintained today." }, { "commit": "0eca14919146d12010da680eb3c19c777dd09a4f", "tree": "221a7330f6550b4726f3bafb0d316041b26df4ad", "parents": [ "4bfb5ee254d0d51ff3250306a119c45501326870" ], "author": { "name": "Pierre Gergondet", "email": "pierre.gergondet@woven.toyota", "time": "Thu May 28 12:56:12 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu May 28 12:56:12 2026" }, "message": "Strip whitespace from paths before prefixing ${pwd} (#4054)\n\nFixes #3992\n\nThis patch strips the relative paths before prefixing `${pwd}`. This\nalso tweaks an existing test to test this situation." }, { "commit": "4bfb5ee254d0d51ff3250306a119c45501326870", "tree": "c507173b7e673ff409678d077930d7ec4c65e644", "parents": [ "92621cdf966857d1c7657c6ac91d1ecf77471101" ], "author": { "name": "Martin Gammelsæter", "email": "mg@axadelta.com", "time": "Wed May 27 21:36:33 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed May 27 21:36:33 2026" }, "message": "Pass --config skip_children\u003dtrue to rustfmt (#4059)\n\nThe rustfmt.toml `skip_children` workaround is a no-op on stable\nrustfmt. Instead, we pass it as a --config flag, which seems to be\nhonored.\n\nFixes #4022" }, { "commit": "92621cdf966857d1c7657c6ac91d1ecf77471101", "tree": "8a634c0886e0628ee69f7ee12c9a79887504e174", "parents": [ "19ce34a811e011b4b56f407e87fa33cb5daa42ff" ], "author": { "name": "Jorge Gorbe Moya", "email": "slack@codemaniacs.com", "time": "Wed May 27 15:15:56 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed May 27 15:15:56 2026" }, "message": "Remove placeholder for Google-internal import macro. (#4058)\n\nThe placeholder is no longer needed for Google to keep using the import\nmacro internally, so we don\u0027t have to keep it in the upstream repo." }, { "commit": "19ce34a811e011b4b56f407e87fa33cb5daa42ff", "tree": "49d16c182f889fa7a74b9e8e3342293a9b3e9dab", "parents": [ "a2d98d6bf693810668b49cd5a81e3c36703034f3" ], "author": { "name": "Alex Trotta", "email": "44127594+Ahajha@users.noreply.github.com", "time": "Fri May 22 16:24:59 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Fri May 22 16:24:59 2026" }, "message": "Add extra_exec_rustc_flags_triples to toolchain attributes (#3911)\n\nWe have:\nextra_rustc_flags\nextra_rustc_flags_triples\nextra_exec_rustc_flags\n, so rounding out the set. Hit this when passing\n`-Clink-self-contained\u003dno` to the toolchain, and this is only available\non x86_64 rust toolchains." }, { "commit": "a2d98d6bf693810668b49cd5a81e3c36703034f3", "tree": "f7cb5c05430a92b08be10520ee1a8ec76b2e4141", "parents": [ "dea48e6108b40905400573bb76c523f88971d831" ], "author": { "name": "UebelAndre", "email": "github@uebelandre.com", "time": "Thu May 21 14:03:38 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Thu May 21 14:03:38 2026" }, "message": "Fix `OUT_DIR` sanitization in `cargo_build_script` (#4050)\n\ncloses https://github.com/bazelbuild/rules_rust/pull/4045" }, { "commit": "dea48e6108b40905400573bb76c523f88971d831", "tree": "8e58f0974f3ee43c61b931076d3c2412b65c5e87", "parents": [ "c821113c2be5b391666e02ad00b0536a647f922e" ], "author": { "name": "Jorge Gorbe Moya", "email": "slack@codemaniacs.com", "time": "Wed May 20 10:28:42 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Wed May 20 10:28:42 2026" }, "message": "Remove is_proc_macro_dep. (#4052)\n\nThis was only used internally at Google during bootstrapping, and it\u0027s\nno longer needed.\n\nCo-authored-by: Krasimir Georgiev \u003ckrasimir@google.com\u003e" }, { "commit": "c821113c2be5b391666e02ad00b0536a647f922e", "tree": "4a32a251d89a33ff262ad8ff5880c21fbff0b75f", "parents": [ "7e46ed660addb62ba301b38d01163d89ad31d38e" ], "author": { "name": "Thomas Anagrius", "email": "anagrius@users.noreply.github.com", "time": "Tue May 19 03:14:55 2026" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "time": "Tue May 19 03:14:55 2026" }, "message": "Update wasm-bindgen to 0.2.121 (#4043)\n\nBumps the bundled `wasm-bindgen`, `wasm-bindgen-cli`, and\n`wasm-bindgen-test` to their latest stable versions (`0.2.121` /\n`0.3.71`). Same shape as #3703; regenerated via `bazel run\n@@//3rdparty:crates_vendor` from the wasm_bindgen extension.\n\nChanges:\n\n- `WASM_BINDGEN_VERSION \u003d \"0.2.121\"` in both `repositories.bzl` and\n`extensions.bzl`\n- `wasm-bindgen-test` spec → `0.3.71`\n- Regenerated `Cargo.Bazel.lock`, `extensions/wasm_bindgen/MODULE.bazel`\n`use_repo` aliases, and the entire `3rdparty/crates/BUILD.*.bazel` set.\n\nMotivation: downstream consumers want crates that need `wasm-bindgen \u003e\u003d\n0.2.108` — for example `wasm-streams 0.5`, pulled in by\n`tonic-web-wasm-client 0.9`+. With the bundled cli pinned at `0.2.105`,\ndownstream code is forced to either vendor-patch `tonic-web-wasm-client`\nback to `0.8` (to keep the schema versions aligned) or write a custom\n`rust_wasm_bindgen_toolchain`." } ], "next": "7e46ed660addb62ba301b38d01163d89ad31d38e" }