chore(deps): bump ngx_wasm_module to prerelease-0.2.0 #12166
Merged
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
flrgh
added
the
cherry-pick kong-ee
team-eng-enablement
added
the
author/community
flrgh
added
backport release/3.5.x
and removed
author/community
Changes since b51a15fc972540e6b8964e2fe1d86ebf67ca53aa: * 388d572 - docs(changelog) prerelease-0.2.0 * 7d3451b - chore(codecov) specify flags in 'flag_management' section * d59027f - chore(valgrind.supp) consolidate wasmparser::parse suppressions * 7184a57 - chore(deps) bump OpenSSL to 3.2.0 * 338bcbe - chore(deps) bump zlib to 1.3 * 743c3d3 - chore(deps) cargo update * 8964b1f - chore(util) minor cleanup/improvements * f955308 - chore(sdk) separate build and install of .wasm examples * 8f3fa95 - fix(wasi) do not use instance pool in 'fd_write' * 4f47e96 - docs(proxy-wasm) document response body buffering * f813a30 - feat(proxy-wasm) implement response body buffering * f171e0f - chore(util) always invoke the Proxy-Wasm SDK scripts * 3d61ca1 - chore(ci) add code coverage for Valgrind jobs * a278bb7 - tests(*) switch Valgrind tests from 'opt-out' to 'opt-in' * 9584c03 - fix(proxy-wasm) use filter chain pool in 'ngx_proxy_wasm_maps_set' * 175f0b8 - chore(util) minor usage fix and style cohesion for scripts * aefb121 - chore(ci) install Node.js in unit and valgrind jobs * e757482 - chore(*) clone and test proxy-wasm-assemblyscript-sdk examples * f2faf97 - chore(util) build Proxy-Wasm SDKs on 'make setup' * bd1b5b8 - chore(ci) remove 'nginx.sock' before artifact upload on failure * 65a0b46 - chore(util) use 'git fetch --tags' for updating runtimes
flrgh
force-pushed
the
chore/deps-bump-ngx-wasm-module
branch
from
e6be9c9 to
8af538f
Compare
flrgh
changed the title
|
@hishamhm this look like what you were after? |
flrgh
approved these changes
Dec 7, 2023
team-eng-enablement
added
the
author/community
|
@flrgh yes, thank you! |
locao
approved these changes
Dec 7, 2023
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.5.x
git worktree add -d .worktree/backport-12166-to-release/3.5.x origin/release/3.5.x
cd .worktree/backport-12166-to-release/3.5.x
git switch --create backport-12166-to-release/3.5.x
git cherry-pick -x aba1910882daefa125c503f4de1d82efab5e4d12 |
|
Cherry-pick failed for Please cherry-pick the changes locally. git remote add upstream https://github.com/kong/kong-ee
git fetch upstream master
git worktree add -d .worktree/cherry-pick-12166-to-master-to-upstream upstream/master
cd .worktree/cherry-pick-12166-to-master-to-upstream
git checkout -b cherry-pick-12166-to-master-to-upstream
ancref=$(git merge-base 89e62669ea26fea36f66bcab092fd507a9abd326 8af538fe082c12bd7e80e5d1d75899fea3e96556)
git cherry-pick -x $ancref..8af538fe082c12bd7e80e5d1d75899fea3e96556 |
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.
Changelog
b51a15f...388d572Compare on GitHub
388d572- docs(changelog) prerelease-0.2.07d3451b- chore(codecov) specify flags in 'flag_management' sectiond59027f- chore(valgrind.supp) consolidate wasmparser::parse suppressions7184a57- chore(deps) bump OpenSSL to 3.2.0338bcbe- chore(deps) bump zlib to 1.3743c3d3- chore(deps) cargo update8964b1f- chore(util) minor cleanup/improvementsf955308- chore(sdk) separate build and install of .wasm examples8f3fa95- fix(wasi) do not use instance pool in 'fd_write'4f47e96- docs(proxy-wasm) document response body bufferingf813a30- feat(proxy-wasm) implement response body bufferingf171e0f- chore(util) always invoke the Proxy-Wasm SDK scripts3d61ca1- chore(ci) add code coverage for Valgrind jobsa278bb7- tests(*) switch Valgrind tests from 'opt-out' to 'opt-in'9584c03- fix(proxy-wasm) use filter chain pool in 'ngx_proxy_wasm_maps_set'175f0b8- chore(util) minor usage fix and style cohesion for scriptsaefb121- chore(ci) install Node.js in unit and valgrind jobse757482- chore(*) clone and test proxy-wasm-assemblyscript-sdk examplesf2faf97- chore(util) build Proxy-Wasm SDKs on 'make setup'bd1b5b8- chore(ci) remove 'nginx.sock' before artifact upload on failure65a0b46- chore(util) use 'git fetch --tags' for updating runtimesIMPORTANT: Remember to scan this commit log for updates to Wasmtime/V8/Wasmer and update
.requirementsmanually as needed