[35.0.0] Revert "update component-model-async plumbing (#11123)"
#11192
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
…)" This reverts commit b221fca.
alexcrichton
changed the title
component-model-async plumbing (#11123)"component-model-async plumbing (#11123)"
pchickey
approved these changes
Jul 7, 2025
alexcrichton
merged commit 1112ac1
into
bytecodealliance:release-35.0.0
325 of 330 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This reverts #11123 on the 35.0.0 release branch which was created just after this PR merged. This is similar to #10938 where I have no concrete reason for doing this other than to de-risk the release branch further. The support landed in #11123 is not usable without future PRs that'll land in the near future, but these PRs won't be backported either. This means that it's a large refactoring on the release branch which while it shouldn't have any affect on things it seems best to de-risk where possible.