feat(websub): advertise the hub on both feeds - #145
Merged
Conversation
Step 5 and 6 of the go-live checklist in wrangler.toml. The D1 binding landed in c588a61, so the hub can now serve subscriptions and it is safe to advertise — advertising first is the failure the spec page warns about. - public/_headers: rel="hub" + rel="self" on /rss.xml and /changelog/rss.xml. - Both RSS endpoints: the atom:link rel="hub" fallback copy. - api-catalog: a `hub` linkset entry. - websub.md: the worked-example callout, and why this is a self-hub rather than an open one. `updated` bumped. ALLOWED_TOPICS in functions/websub.ts lists exactly the two rel="self" URLs now advertised, so all three copies of the topic list agree. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
40ba5d6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://28819a74.specification-website.pages.dev |
| Branch Preview URL: | https://feat-websub-go-live-2026-07.specification-website.pages.dev |
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
1 participant
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.
Steps 5 and 6 of the go-live checklist in
wrangler.toml. The D1 binding landed separately in c588a61, so the hub can actually serve subscriptions — this is the commit that makes it discoverable.Order matters here and this is the safe direction. A
rel="hub"link with nothing behind it is the exact failure the spec page names: "an advertisement is not a delivery mechanism." Binding first, advertisement second.What changed
public/_headers—rel="hub"andrel="self"on/rss.xmland/changelog/rss.xml. This is the authoritative copy; subscribers check headers before embedded elements (WebSub §4).src/pages/rss.xml.tsandsrc/pages/changelog/rss.xml.ts— the<atom:link rel="hub">fallback inside each feed body.api-catalog— ahublinkset entry.websub.md— the worked-example callout CLAUDE.md requires once the site is an example of its own page. It says explicitly that this is a self-hub withhub.topicallowlisted to our two feeds, and that pointing at a hosted hub is the ordinary choice — so the page doesn't read as "you should run one too".updatedbumped.Consistency check
_headerswarns to keep three copies of the topic list in sync.ALLOWED_TOPICSinfunctions/websub.tslists exactly the tworel="self"URLs now advertised. All three agree.Checks
npm run build✓ ·npm run lint✓ ·npm run format:check✓ ·npm run test:websub✓ ·npm run check:skill✓ (166 pages)Verified in the built output rather than the source: both
dist/rss.xmlanddist/changelog/rss.xmlcarry<atom:link href="https://specification.website/websub" rel="hub"/>, andapi-catalogre-parses as valid JSON.Still to do after merge (step 7)
curl -sI https://specification.website/rss.xmlonce Pages deploys and confirm theLinkheader carriesrel="hub"in production.workflow_dispatchrun ofwebsub-pingshould return 202 — yours, since it needs the Actions secret and fans out to any live subscribers.subscribe → verify → distributehas still never been exercised end to end. Neither check above proves a real handshake. websub.rocks pointed at/websubwould.🤖 Generated with Claude Code