w3c / browser-specs

A machine-readable list of Web specifications
Other
224 stars 44 forks source link

Add new spec: A Well-Known URL for Passkey Endpoints #1291

Closed dontcallmedom closed 7 months ago

dontcallmedom commented 7 months ago

URL

https://w3c.github.io/webappsec-passkey-endpoints/passkey-endpoints.html

Rationale

Adopted by the WebAppSec Working Group

Additional properties

{"nightly":{"sourcePath": "passkey-endpoints.bs"}}
browser-specs-bot commented 7 months ago

Changes to index.json

This update would trigger the following changes in index.json:

Add spec (1) ```json { "url": "https://w3c.github.io/webappsec-passkey-endpoints/passkey-endpoints.html", "seriesComposition": "full", "shortname": "passkey-endpoints", "series": { "shortname": "passkey-endpoints", "currentSpecification": "passkey-endpoints", "title": "A Well-Known URL for Passkey Endpoints", "shortTitle": "A Well-Known URL for Passkey Endpoints", "nightlyUrl": "https://w3c.github.io/webappsec-passkey-endpoints/passkey-endpoints.html" }, "nightly": { "url": "https://w3c.github.io/webappsec-passkey-endpoints/passkey-endpoints.html", "status": "Editor's Draft", "sourcePath": "passkey-endpoints.bs", "alternateUrls": [], "repository": "https://github.com/w3c/webappsec-passkey-endpoints", "filename": "passkey-endpoints.html" }, "organization": "W3C", "groups": [ { "name": "Web Application Security Working Group", "url": "https://www.w3.org/groups/wg/webappsec/" } ], "title": "A Well-Known URL for Passkey Endpoints", "source": "spec", "shortTitle": "A Well-Known URL for Passkey Endpoints", "categories": [ "browser" ], "standing": "good" } ```

Tests

These changes look good! 😎

tidoust commented 7 months ago

@browser-specs-bot pr

tidoust commented 7 months ago

For some reason, the job was skipped. Perhaps the job does not see me as "MEMBER"? @dontcallmedom, could you give it a try yourself?

dontcallmedom commented 7 months ago

@browser-specs-bot pr

dontcallmedom commented 7 months ago

it looks like @browser-specs-bot is rebelling against its creator

tidoust commented 7 months ago

I'm going to reuse this issue to make tests. You may ignore the comments (and any created PR if one gets created, although none should be in practice, since the spec is now in specs.json).

@browser-specs-bot pr

tidoust commented 7 months ago

OK, that worked (and didn't create a PR, which is good too!). I hadn't realized that my W3C membership on GitHub was "private". Actually, I hadn't paid attention to that setting until today. ;)

I suspect that the job lies to preserve my privacy (don't know who that person is, certainly not a member!). That makes sense. Making my membership "public" solved the issue.