Work around stale Xcode version from outer Bazel invocation #3232
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We were potentially setting a stale `--version` in `runner.sh`, because not everyone (including the local dev environment of this ruleset) has code in `tools/bazel` to force Bazel to re-evaluate its Xcode cache when `xcode-select -p` changes. Now we follow more of https://github.com/bazelbuild/rules_apple/blob/master/doc/common_info.md#xcode-version-selection-and-invalidation. Signed-off-by: Brentley Jones <[email protected]>
brentleyjones
force-pushed
the
bj/work-around-stale-xcode-version-from-outer-bazel-invocation
branch
from
616552a to
c68a8bb
Compare
luispadron
approved these changes
Oct 31, 2025
brentleyjones
deleted the
bj/work-around-stale-xcode-version-from-outer-bazel-invocation
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were potentially setting a stale
--versioninrunner.sh, because not everyone (including the local dev environment of this ruleset) has code intools/bazelto force Bazel to re-evaluate its Xcode cache whenxcode-select -pchanges. Now we follow more of https://github.com/bazelbuild/rules_apple/blob/master/doc/common_info.md#xcode-version-selection-and-invalidation.