Skip to content

docs(README): update deployment notice — cyclic.app is dead - #250

Merged
Kshitij978 merged 1 commit into
Ashutosh00710:mainfrom
MAqilNaufal:fix/dead-cyclic-deployment-link
May 13, 2026
Merged

docs(README): update deployment notice — cyclic.app is dead#250
Kshitij978 merged 1 commit into
Ashutosh00710:mainfrom
MAqilNaufal:fix/dead-cyclic-deployment-link

Conversation

@MAqilNaufal

Copy link
Copy Markdown
Contributor

Issue

The 'Deployment Moved' notice near the top of the README directs users to:

`https://github-readme-activity-graph.cyclic.app\`

as the canonical deployment, with the Vercel URL listed only as a fallback. But Cyclic.sh shut down in early 2025 and that domain no longer resolves. New users who follow the notice literally hit a DNS failure before they get to the working Vercel deployment further down the doc.

Fix

Reword the notice so:

  • `github-readme-activity-graph.vercel.app` is the canonical deployment.
  • The old Heroku and Cyclic URLs are marked as historical.
  • The link to issue BUG: This graph was stopped working.  #197 is preserved for context.

One-paragraph README edit, no other changes.

Verification

  • The current Vercel deployment at `github-readme-activity-graph.vercel.app` is up and serving the activity graph used by many profile READMEs.
  • Cyclic.sh wind-down was announced and the platform shut down end of 2024 / early 2025.

The 'Deployment Moved' notice still points users at
github-readme-activity-graph.cyclic.app as the primary deployment, but
Cyclic.sh shut down in early 2025 and that domain no longer resolves.
The Vercel deployment is currently the only reachable one. Reword the
notice to make Vercel canonical and mark the Heroku + Cyclic URLs as
historical.
@vercel

vercel Bot commented May 12, 2026

Copy link
Copy Markdown

@MAqilNaufal is attempting to deploy a commit to the ashutosh00710's projects Team on Vercel.

A member of the Team first needs to authorize it.

@Kshitij978
Kshitij978 merged commit 81f24f9 into Ashutosh00710:main May 13, 2026
1 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants