Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 2, 2025

This PR contains the following updates:

Package Update Change
bazel major 7.7.18.5.0

Release Notes

bazelbuild/bazel (bazel)

v8.5.0

Compare Source


Release Notes:

v8.4.2

Compare Source


Release Notes:

v8.4.1

Compare Source


Release Notes:

v8.4.0

Compare Source


Release Notes:

v8.3.1

Compare Source

[!NOTE]
If you are looking for rolling releases, please visit this page.

Release 8.3.1 (2025-06-30)

Bazel 8.3.1 is a patch LTS release. It is fully backward compatible with Bazel 8.0 and contains selected changes by the Bazel community and Google engineers.

  • Removed the "overwrote runfiles" warning related to rules_shell. (#​26374)
  • Reverted the change to move the Bash runfiles library out of Bazel. This will be delayed until 9.0. (#​26372)
  • Fixed hang with force fetching + repo contents cache (#​26412)

Refer to the full list of commits for more details.

Notice: Bazel installers contain binaries licensed under the GPLv2 with Classpath exception. Those installers should always be redistributed along with the source code.

Some versions of Bazel contain a bundled version of OpenJDK. The license of the bundled OpenJDK and other open-source components can be displayed by running the command bazel license. The vendor and version information of the bundled OpenJDK can be displayed by running the command bazel info java-runtime. The binaries and source-code of the bundled OpenJDK can be downloaded from our mirror server.

Security: All our binaries are signed with our public key 3D5919B.

v8.3.0

Compare Source


Release Notes:

v8.2.1

Compare Source


Release Notes:

v8.2.0

Compare Source


Release Notes:

v8.1.1

Compare Source


Release Notes:

v8.1.0

Compare Source


Release Notes:

v8.0.1

Compare Source


Release Notes:

v8.0.0

Compare Source


Release Notes:


Configuration

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

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

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

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


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 6dd50b5 to 82adf3a Compare July 10, 2025 20:17
@jacky8hyf
Copy link
Collaborator

I would hold this until I figure out how to keep the CI against Bazel 7.x. Right now, with this change, only 8.0 and 8.3.1 would be tested against.

jacky8hyf added a commit to jacky8hyf/rules_devicetree that referenced this pull request Jul 16, 2025
jacky8hyf added a commit that referenced this pull request Jul 16, 2025
Needed for #19 to update to Bazel 8.
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 82adf3a to a02bf59 Compare July 16, 2025 19:04
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from a02bf59 to 63d4379 Compare September 4, 2025 21:08
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 63d4379 to a4791a5 Compare September 12, 2025 03:49
@renovate renovate bot force-pushed the renovate/bazel-8.x branch 3 times, most recently from dec196f to 734a8f4 Compare October 1, 2025 20:55
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 734a8f4 to 006dc64 Compare October 8, 2025 23:31
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 006dc64 to 43ab3cb Compare October 31, 2025 19:33
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 43ab3cb to 8db0651 Compare December 11, 2025 22:10
@renovate renovate bot force-pushed the renovate/bazel-8.x branch from 8db0651 to 80652cc Compare January 2, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants