Merge upstream main branch #23
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
This is necessary for Bikeshed to generate CRs.
…Assembly#1785) In addition to testing `demote(x-promote(y))`, also test `demote(promote(y) - x)`. And test similar mixed-type cases for multiply and divide.
Add a sqrt test for values around ¼, where `sqrt(x) - x` is greatest. And add a few more sqrt test values based on divergences in sqrt implementations found in the wild.
This is derived from WebAssembly#1764 but does not actually change the publication status by default locally or on CI (ED is the default, and the w3c echidna publication action overrides it to WD). It also includes a fix to the echidna Makefile rules to exit with an error in case an underlying step returns an error.
Also needed for CR generation
…#1791) When manually dispatching workflows, inputs can be collected from the dispatching user and passed to the workflow. Use this feature to allow manually setting the W3C_STATE of the document. This will let us publish CR drafts on every push (once we update the default state from WD) and CR snapshots on demand. Co-authored-by: Ms2ger <[email protected]>
The Makefiles now generate a date 30 days in the future, and pass this date to bikeshed as the standard 'Deadline' metadata. Along with speced/bikeshed-boilerplate#98, this causes the document status section to generate with a transition deadline always 30 from the generation time.
…bAssembly#1803) The w3c-status options correspond to the valid options for Bikeshed's --md-status flag (i.e. Status metadata, https://speced.github.io/bikeshed/#metadata), and refer to the W3C rec-track document stages described in https://www.w3.org/policies/process/#maturity-stages (Editor's Draft, Working Draft, Candidiate Recommendation Draft, and Candidate Recommendation Snapshot).
…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.
Pulls in a fix for CI