forked from WebAssembly/spec
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Merge with WebAssembly/spec #51
Merged
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
…sembly#1813) This reverts commit 5042950. There is will allow publishing more WD builds until the CR transition finishes.
…y#1814) These sections provide a bit more background about their relationship to the layer beneath them. They also solve the problem that the existing minimal introductory text was hidden in the bottom of the "status of this document" section.
Co-authored-by: Ms2ger <[email protected]> Co-authored-by: Andreas Rossberg <[email protected]>
…ebAssembly#1818) These considerations are aimed at answering the questions to consider from the TAG security and privacy questionnaire: https://www.w3.org/TR/security-privacy-questionnaire/
…1821) * The API call does not return its results synchronously, so the status check script polls for the result and exits with an error if it fails. * The Makefiles and CI workflow introduce the ability to run the publishing step as a dry run, so it can be used with pull requests. * CI also supports the ability to use W3C username and password secrets instead of Echidna tokens
…ly#1825) This ensures that all 3 specs build and upload even if one fails. Also use 'uploaded' in the status text instead of 'published' to reflect possible dry run or validation failure.
…1826) Fix a sequence that Bikeshed is treating as a macro and rewriting. This is a workaround for WebAssembly#1823
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.
No description provided.