Merge main into next: canonical URL, retire GitHub Pages - #115
Merged
Conversation
audiobrowser.dev is served by Cloudflare Pages now, built from this branch on every push. docs.yml was deploying a second, competing build of the same site to GitHub Pages, and website/CNAME only ever meant anything to that host. The GitHub Pages site itself is unbound from the repo separately — deleting the workflow stops new deployments but does not release the domain. Not removed: the _github-pages-challenge-radio-garden TXT record. It holds GitHub's org-level verification of audiobrowser.dev, and while it exists no other GitHub account can claim the domain for Pages.
The Pages project answers on audiobrowser.pages.dev as well as audiobrowser.dev, serving the same production build from the same commit. Two hostnames with identical content compete in search results; a canonical URL points both at audiobrowser.dev. Skipped for DOCS_NOINDEX builds. A page that is both noindexed and canonicalised elsewhere sends contradictory signals, and previews are already noindexed, so there is nothing left to disambiguate.
docs: retire the GitHub Pages deployment, declare a canonical URL
Brings the canonical URL and removes the GitHub Pages deployment. next still carried its own copy of docs.yml. Harmless on this branch — it only ever triggered on pushes to main — but merging next back into main would have resurrected the workflow and started a second, competing deploy of the site alongside Cloudflare Pages. website/CNAME goes for the same reason. Clean merge; no conflicts.
|
🎉 This PR is included in version 0.2.0-next.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Brings
main(#114) intonext.Why it matters for this branch
nextstill carried its own copy of.github/workflows/docs.yml. Harmless here — it only ever triggered on pushes tomain— but mergingnextback intomainwould have resurrected the workflow and started a second, competing deploy of the site alongside Cloudflare Pages.website/CNAMEgoes for the same reason: it only ever meant anything to GitHub Pages.Also brings the canonical URL, so preview builds share production's config rather than drifting from it.
Verification
Production build:
DOCS_NOINDEX=1build: zero canonical tags,_headerswithX-Robots-Tag: noindex, nofollow.Clean merge, no conflicts.
yarn ci:formatandyarn ci:lintpass.