Skip to content

Update Envoy to 4113c85 (Nov 05, 2026) - #1650

Merged
tomjzzhang merged 1 commit into
envoyproxy:mainfrom
fei-deng:update_nov
Nov 10, 2026
Merged

tomjzzhang merged 1 commit into
envoyproxy:mainfrom
fei-deng:update_nov

Conversation

@fei-deng

@fei-deng fei-deng commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Update Envoy dependency to envoyproxy/envoy@4113c85 (Nov 05, 2026).

  • Sync ENVOY_COMMIT, bazel_dep pins (envoy_toolshed), bazel-registry SHA in .bazelrc, and Python requirements.
  • Sync build image SHAs in .github/config.yml, ci/envoy_build_sha.sh, and ci/run_envoy_docker.sh.
  • Update docs/root/updating_envoy_dependency.md to clarify ENVOY_COMMIT update instructions.

@fei-deng
fei-deng force-pushed the update_nov branch 4 times, most recently from 05961aa to 1736299 Compare November 6, 2026 15:39
@fei-deng fei-deng added the waiting-for-review A PR waiting for a review. label Nov 6, 2026

@tomjzzhang tomjzzhang left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for update! Left a few small inline questions on .bazelrc, plus a couple of general questions:

  1. It looks like envoyproxy/envoy#48963 was missed/reverted in ci/run_envoy_docker.sh (Step 8) — did that cause a CI issue with the minimal ci image, or should we sync ci/run_envoy_docker.sh as well?
  2. It looks like Step 13 (tools/code_format/config.yaml) was also missed (envoyproxy/envoy#39632 removed - bazel/rbe/toolchains/configs/)?
  3. Could we update the PR description to match your latest commit message (which covers the GCC toolchain and test_integration_basics.py changes)?

Comment thread .bazelrc Outdated
build:gcc --config=libstdc++
# Select the opt-in GCC toolchain for target and execution configurations.
build:gcc --@envoy//bazel:use_gcc
build:gcc --host_platform=@clang_platform

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we mark this with # unique (per Step 9 of updating_envoy_dependency.md) so future merge_from_envoy runs don't overwrite it?

Suggested change
build:gcc --host_platform=@clang_platform
build:gcc --host_platform=@clang_platform # unique

Comment thread .bazelrc
build:gcc --cxxopt=-Wno-dangling-reference
build:gcc --cxxopt=-Wno-nonnull-compare
build:gcc --cxxopt=-Wno-trigraphs
build:gcc --linkopt=-fuse-ld=gold --host_linkopt=-fuse-ld=gold

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It looks like a couple of .bazelrc hunks from Step 10 (merge_from_envoy) were missed in this commit range — should we include them here?

Comment thread .bazelrc
common:remote-exec --remote_executor=grpcs://mordenite.cluster.engflow.com
common:remote-exec --jobs=200
common:remote-exec --define=engflow_rbe=true
common:remote-exec --host_platform=@clang_platform

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we also need info:remote-exec --host_platform=@platforms//host here (matching Envoy's ci.bazelrc and info:clang on line 166) so bazel info --config=rbe doesn't fail before @clang_platform is fetched?

Suggested change
common:remote-exec --host_platform=@clang_platform
common:remote-exec --host_platform=@clang_platform
info:remote-exec --host_platform=@platforms//host


Edit [MODULE.bazel](/MODULE.bazel):

Update the `ENVOY_COMMIT` variable with the target Envoy commit hash:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: extra spaces and ).: at the end:

Suggested change
Update the `ENVOY_COMMIT` variable with the target Envoy commit hash:
Update `ENVOY_COMMIT` to the latest Envoy's commit from
[this page](https://github.com/envoyproxy/envoy/commits/main) (clicking on the
short commit id opens a page that contains the fully expanded commit id):

Update Envoy dependency to envoyproxy/envoy@4113c85 (Nov 05, 2026).

- Sync ENVOY_COMMIT, bazel_dep pins (envoy_toolshed), bazel-registry SHA in .bazelrc, tools/code_format/config.yaml, and Python requirements.
- Sync build image SHAs and docker runner in .github/config.yml, ci/envoy_build_sha.sh, and ci/run_envoy_docker.sh (with ENVOY_DOCKER_DEVTOOLS=1 in _ci.yml).
- Register downstream hermetic GCC toolchain following upstream Envoy toolchain migration (envoyproxy/envoy#39632).
- Set --host_platform=@clang_platform for GCC and remote execution in .bazelrc, and update GCC CI linker flag from gold's --no-threads to lld's --threads=1.
- Increase output format test durations in test_integration_basics.py for TSAN stability.
- Update docs/root/updating_envoy_dependency.md to clarify ENVOY_COMMIT update instructions.

Signed-off-by: fei-deng <101672975+fei-deng@users.noreply.github.com>
@fei-deng

Copy link
Copy Markdown
Contributor Author

Thanks for the thorough review! Addressed all comments:

Synced ci/run_envoy_docker.sh with envoyproxy/envoy#48963 and set ENVOY_DOCKER_DEVTOOLS: '1' in .github/workflows/_ci.yml (the minimal ci image lacks host python3, which caused bazel run //tools:check_envoy_includes.py in check_format to fail).
Synced tools/code_format/config.yaml and the missed .bazelrc hunks, added # unique to build:gcc --host_platform=@clang_platform, added info:remote-exec --host_platform=@platforms//host, and fixed the nit in docs/root/updating_envoy_dependency.md.
Updated the PR description to match the latest commit message.

@tomjzzhang
tomjzzhang merged commit 1abc63f into envoyproxy:main Nov 10, 2026
16 of 17 checks passed
@fei-deng fei-deng removed the waiting-for-review A PR waiting for a review. label Nov 10, 2026
@fei-deng
fei-deng deleted the update_nov branch November 10, 2026 22:51
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