[CHORE](redirects) Auto redirect from prior releases address#401
Conversation
Signed-off-by: John McCall <john@overturemaps.org>
There was a problem hiding this comment.
Pull request overview
Adds a client-side redirect from the legacy /releases path to the current /release-calendar/ page by introducing the @docusaurus/plugin-client-redirects plugin and configuring a single redirect entry.
Changes:
- Add
@docusaurus/plugin-client-redirects@^3.10.1dependency. - Register the plugin in
docusaurus.config.jswith a/releases→/release-calendar/redirect.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Adds the client redirects plugin dependency. |
| package-lock.json | Lockfile entry for the new plugin. |
| docusaurus.config.js | Configures the plugin with the /releases → /release-calendar/ redirect. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🗺️ OMF Docs previews are live!
Auto-gen schema site is now available. This is an early preview of a future workflow where we will automatically generate and publish reference docs for the Overture Maps Format schema. The auto-gen schema site may contain incomplete or inaccurate information as we are still refining the generation process, so please compare against the repo schema site and refer to the official Overture documentation for authoritative information. Note ♻️ This preview updates automatically with each push to this PR. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Alex Iannicelli (atiannicelli)
left a comment
Alex Iannicelli (atiannicelli)
left a comment
There was a problem hiding this comment.
Sounds good to me
John McCall (lowlydba)
deleted the
375-handle-traffic-to-old-releases-page-in-docs
branch
Per the issue, this will give us a redirect from
/releasesto resurrect any dead URLs that were not updated to point to/release-calendar.Note
Due to the janky CloudFront setup for the staging deploy, it won't work (well) - but this works as expected locally, and will work in production (GH Pages based)