Skip to content

envoy: Bump to version v1.38.3#1917

Open
sayboras wants to merge 5 commits into
mainfrom
pr/tammach/envoy-1.38
Open

envoy: Bump to version v1.38.3#1917
sayboras wants to merge 5 commits into
mainfrom
pr/tammach/envoy-1.38

Conversation

@sayboras

Copy link
Copy Markdown
Member

No description provided.

@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch 2 times, most recently from d5b580a to 2eae317 Compare May 24, 2026 02:23
@sayboras sayboras changed the title Pr/tammach/envoy 1.38 envoy: Bump to version v1.38.0 May 24, 2026
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch 3 times, most recently from 70e29a9 to 7029cc2 Compare May 24, 2026 08:44
@sayboras
sayboras marked this pull request as ready for review May 24, 2026 08:52
@sayboras
sayboras requested a review from a team as a code owner May 24, 2026 08:52
@sayboras
sayboras requested review from jrajahalme and nezdolik May 24, 2026 08:52
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch 3 times, most recently from e1f065a to 5cb5823 Compare June 8, 2026 14:49
@sayboras sayboras changed the title envoy: Bump to version v1.38.0 envoy: Bump to version v1.38.1 Jun 9, 2026
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch 3 times, most recently from b4144d9 to 91a45f1 Compare June 11, 2026 14:11
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch from 91a45f1 to 83505c6 Compare June 16, 2026 11:42
@sayboras sayboras changed the title envoy: Bump to version v1.38.1 envoy: Bump to version v1.38.2 Jun 16, 2026
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch from 83505c6 to 836f9ae Compare June 26, 2026 11:15
@sayboras sayboras changed the title envoy: Bump to version v1.38.2 envoy: Bump to version v1.38.3 Jul 1, 2026
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch from 836f9ae to f43d4d1 Compare July 1, 2026 15:50
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch from f43d4d1 to a959f21 Compare July 9, 2026 10:40
@@ -1,7 +1,19 @@
From 1d2c987eee776d0a0ac1df6724edf02d9bb4da3a Mon Sep 17 00:00:00 2001
From: Tam Mach <sayboras@yahoo.com>
Date: Sat, 23 May 2026 22:46:20 +1000

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.

i believe the patch has been merged to upstream, do we still need it here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This fix landed on main (envoyproxy/envoy#45029) after release/v1.38 was cut and wasn't backported, so we still need this patch until we bump to v1.39+.

sayboras added 4 commits July 17, 2026 22:13
Signed-off-by: Tam Mach <tam.mach@cilium.io>
Signed-off-by: Tam Mach <tam.mach@cilium.io>
Envoy 1.38's clang-format configuration requires:
- Space before {} in aggregate initialization
- Space before .field in validate.rules annotations

Signed-off-by: Tam Mach <tam.mach@cilium.io>
Envoy 1.38's check_format depends on @llvm_toolchain_llvm//:clang-format,
but in system-LLVM mode (BAZEL_LLVM_PATH) the repo envoy creates lacks that
target. Pre-create a complete @llvm_toolchain_llvm before envoy_toolchains()
so it is reused for both compilation and the format check.

Signed-off-by: Tam Mach <sayboras@yahoo.com>
@sayboras
sayboras force-pushed the pr/tammach/envoy-1.38 branch from a959f21 to 74ec34b Compare July 17, 2026 12:13
The switch from the local envoy_dependency_imports.bzl fork to Envoy's
upstream dependency_imports.bzl changed the crate_universe config that
rules_rust hashes into the lockfile digest, so CI failed fetching
@envoy_rust_crate_index with a digest mismatch. Refresh the lockfile
with 'make cargo-repin' against the current wiring.
@sayboras
sayboras requested a review from nezdolik July 17, 2026 12:34
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