-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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.
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
chore(build): rename rust target wasm32-wasi to wasm32-wasip1 #13708
Merged
Conversation
This file contains 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
added
chore
Not part of the core functionality of kong, but still needed
build/bazel
cherry-pick kong-ee
schedule this PR for cherry-picking to kong/kong-ee
labels
Sep 24, 2024
flrgh
force-pushed
the
chore/wasm-filter-target-rename
branch
from
September 24, 2024 17:31
0b1fef1
to
3f4ebf4
Compare
flrgh
changed the title
WIP: rename wasm32-wasi => wasm32-wasip1
chore(build): rename rust target wasm32-wasi to wasm32-wasip1
Sep 24, 2024
team-gateway-bot
added
the
author/community
PRs from the open-source community (not Kong Inc)
label
Sep 24, 2024
flrgh
removed
the
author/community
PRs from the open-source community (not Kong Inc)
label
Sep 25, 2024
team-gateway-bot
added
the
author/community
PRs from the open-source community (not Kong Inc)
label
Sep 25, 2024
flrgh
force-pushed
the
chore/wasm-filter-target-rename
branch
from
October 22, 2024 22:43
3f4ebf4
to
727ea86
Compare
@flrgh it looks like this is failing for the build & test step. Does the new wasm32-wasip1 target move the files to a different directory? Maybe target/wasm32-wasip1? |
brentos
approved these changes
Oct 23, 2024
team-eng-enablement
removed
the
author/community
PRs from the open-source community (not Kong Inc)
label
Nov 4, 2024
flrgh
force-pushed
the
chore/wasm-filter-target-rename
branch
from
January 8, 2025 17:50
a3b3f58
to
cead534
Compare
tzssangglass
approved these changes
Jan 10, 2025
Would this PR be backported? Many versions have this problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
build/bazel
cherry-pick kong-ee
schedule this PR for cherry-picking to kong/kong-ee
chore
Not part of the core functionality of kong, but still needed
size/S
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.
See https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html and rust-lang/rust#126662
Note: this only affects filters built/used for integration tests.