Repository navigation
Release v1.3.0: redesign, credible disclosure and verified tooling - #12
Merged
Merged
Conversation
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
12 of 15 tasks
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
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.
Change
Release v1.3.0 replaces the manifesto landing page with a typographic reference in all 22 languages. It removes the maintainer-only signature list, assumed human approval and unsupported adoption claims; the project page now explains evidence and pending review.
The upgrade also repairs JSON-LD and JSON Schemas, updates dependencies, fixes MCP packaging and validation, improves README/licensing/policy references, and adds browser, accessibility and protocol checks to the release workflow. Release assets include all 54 marks, the vocabulary, both schemas and an installable MCP archive.
Compatibility
Existing workflow numbers and decision branches are unchanged from v1.2.0. The rhetorical Level 5 sentence about legitimacy is removed in every language. The unresolved Level 3 review shortcut is exposed in the wizard and MCP output; its full definition still requires meaningful review. Retired signing URLs redirect to project information.
CG metadata follows the three text values in the 9 October report.
w3cAiDisclosureis now nullable for Levels 1 and 2 because scope/review cannot be inferred. Generic snippets omit the CG declaration; publishers must assess it independently. CodeQL's resource-URL alert is fixed by comparing parsed origins rather than domain prefixes.The 21 translations remain marked as machine translations. Editorial review of this revision is pending. MCP is packaged as an archive and remains unpublished on npm. Standards submissions are tracked in #11; submission does not imply acceptance or Google support.
Verification
npm run verify: types, build, vocabulary/classifier checks and all 352 generated pages passed.BROWSER_CHANNEL=chrome npm run test:browser: all 22 homepages, responsive core routes, keyboard/clipboard/themes, 32 wizard paths, no-JavaScript behavior and automated WCAG A/AA checks passed.npm run test:server --prefix mcp: initialization, four tools, six results, invalid inputs and resource access passed.Remote CI and CodeQL must pass before merging. Safari/Firefox were not separately tested.