Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.26] bump envoy-fork for Feb 8 patches #308

Merged
merged 2 commits into from
Feb 13, 2024
Merged

[1.26] bump envoy-fork for Feb 8 patches #308

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e789a4
bump envoy-fork
jbohanon Feb 12, 2024
d0cbfc7
bump to release and add changelog
jbohanon Feb 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions bazel/repository_locations.bzl
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,8 @@
REPOSITORY_LOCATIONS = dict(
envoy = dict(
# envoy 1.26.5 forked with extproc changes
# sourced from release/v1.26-backportedfork
# should go back to upstream once 1.28or wherever the associated prs are merged
# additionally, add cherry-picked tap filter output sink changes on top
# of above-mentioned ext-proc changes
commit = "2d0040ccb6f24d69d4a5b101c9b95b3e192fc345",
# envoy 1.26.7 forked with extproc changes
# sourced from release v1.26.7-fork1
commit = "37f7ac716a3253001640ccb4a548d8dba0d6cf4f",
remote = "https://github.com/solo-io/envoy-fork",
),
inja = dict(
Expand Down
7 changes: 7 additions & 0 deletions changelog/v1.26.7-patch1/cve-envoy-bump.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
changelog:
- type: DEPENDENCY_BUMP
dependencyOwner: solo-io
dependencyRepo: envoy-fork
dependencyTag: v1.26.7-fork1
issueLink: https://github.com/solo-io/solo-projects/issues/5778
resolvesIssue: false
Loading