Use forked wkg to publish WITs for now #3316
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
Signed-off-by: itowlson <[email protected]>
fibonacci1729
approved these changes
Oct 21, 2025
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.
We believe the auth errors when trying to publish WITs are down to an infelicity between
wkganddocker-credential.We have a candidate fix for this (bytecodealliance/wasm-pkg-tools#176) but are dubious about whether it is safe to roll out for general use, due to different conventions across the Docker ecosystem.
In the interim, we believe the candidate fix works for our specific case, so this PR proposes to use it as an interim solution, so that we can prove that it doesn't work after all and Ivan has been barking up the wrong tree all day.