Skip to content

build: remove redundant Bazel lockfile update workarounds#3553

Merged
alan-agius4 merged 1 commit intoangular:mainfrom
alan-agius4:bazel-lockfile
Mar 17, 2026
Merged

build: remove redundant Bazel lockfile update workarounds#3553
alan-agius4 merged 1 commit intoangular:mainfrom
alan-agius4:bazel-lockfile

Conversation

@alan-agius4
Copy link
Copy Markdown
Contributor

@alan-agius4 alan-agius4 commented Mar 17, 2026

Renovate now natively supports updating Bazel lockfiles.

This change removes the postUpgradeTasks workaround in Renovate presets and a redundant synchronization step in the sync-all-modules.sh script that were previously used to manually update Bazel lockfiles.

Renovate now natively supports updating Bazel lockfiles.

This change removes the `postUpgradeTasks` workaround in Renovate presets and
a redundant synchronization step in the `sync-all-modules.sh` script that
were previously used to manually update Bazel lockfiles.
@alan-agius4 alan-agius4 added the action: blocked The action is blocked by something, such as an upstream update, or an announcement label Mar 17, 2026
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Mar 17, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly removes redundant workarounds for Bazel lockfile updates, following Renovate's new native support. The changes in renovate-presets/default.json5 and tools/sync-all-modules.sh are appropriate. I have added a comment to tools/sync-all-modules.sh suggesting further optimizations to improve the script's efficiency by removing additional redundant lockfile update commands.

I am having trouble creating individual review comments. Click here to see my feedback.

tools/sync-all-modules.sh (9-10)

medium

While removing this initial redundant lockfile update is a good optimization, the script still contains other inefficiencies that could be addressed to improve performance and clarity.

  1. The sync-module-bazel command, called on line 22, already updates the Bazel lockfile. The subsequent call on line 26 is therefore redundant and can be removed.
  2. The loop on lines 32-38 repeatedly runs bazel mod deps --lockfile_mode=update. Since this command operates on the workspace root regardless of the directory it's run from, this loop can be replaced by a single call after the first loop completes.

Addressing these points would make the script more efficient.

@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: blocked The action is blocked by something, such as an upstream update, or an announcement labels Mar 17, 2026
)

# Update the root lockfile. This is needed for the sync-module-bazel command to work due to circular dependencies.
"$BAZEL" mod deps --lockfile_mode=update
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Will renovate not find all of the bazel lockfiles?

Copy link
Copy Markdown
Contributor Author

@alan-agius4 alan-agius4 Mar 17, 2026

Choose a reason for hiding this comment

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

Due to circular dependencies, we still need to run this when we update the TS version from the package.json

Copy link
Copy Markdown
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@alan-agius4 alan-agius4 merged commit a1923f6 into angular:main Mar 17, 2026
13 checks passed
@alan-agius4
Copy link
Copy Markdown
Contributor Author

This PR was merged into the repository. The changes were merged into the following branches:

@alan-agius4 alan-agius4 deleted the bazel-lockfile branch March 17, 2026 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants