Question: About releases page "There aren’t any releases here"

[baijiangjie]

Select Topic Area

Question

Body

After I use the command to quickly delete the draft releases in the repository, the Releases page shows:

gh release list --repo baijiangjie/CordysCRM --json tagName,isDraft -q '.[] | select(.isDraft==true) | .tagName' \
| xargs -I {} gh release delete {} --repo baijiangjie/CordysCRM --yes

https://github.com/baijiangjie/CordysCRM/releases
There aren’t any releases here

However, when I visit https://github.com/baijiangjie/CordysCRM/releases/tag/v1.3.1, the release actually exists.

When I am not logged in to my account, the page displays normally.

However, once I log in with my account, it does not display correctly.

[DP-Hridayan]

Same with my repository. I have 44 releases but visiting the releases page shows "No releases".

https://github.com/DP-Hridayan/aShellYou/releases .

But if I manually visit the page 3 of my releases through url, then the releases start to appear

https://github.com/DP-Hridayan/aShellYou/releases?page=3

[baijiangjie]

Yes, when I add the page (such as: page=2) parameter, it appears, but the default page still doesn’t display.

[Saad200724]

🐞 Solution for Missing Releases When Logged In

This is a recurring bug that has been reported in the GitHub community, where the authenticated user experience shows the "There aren't any releases here" message, even when releases are present.

The issue often lies with how GitHub caches data or renders the view for the logged-in user.

1. Workarounds (Immediate Fixes)

These steps usually resolve the temporary display bug:

• Bypass the Cache (Force Reload): Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to perform a hard refresh, which clears the browser's cache for the page.
• Clear Browser Data: Clear your cookies and cache specifically for github.com and then log back in.
• Use the Paged URL: As the commenter noted, appending ?page=2 (or any other page number if you have many) forces the system to render a different view, which often brings all releases back into the display when you navigate back to page 1.
• Change Repository Visibility (Temporary): If the repository is Private, temporarily switch it to Public and then back to Private. This often forces a complete re-indexing of the repository's features by GitHub's servers.

2. Check for Hidden Filter or Setting

For some users, a setting may have been inadvertently disabled:

• Check Release Filters: Navigate to your repository's main page. Sometimes, there is a small filter or gear icon near the "About" section or the Releases link. Ensure that releases are set to be visible or not filtered out.

3. Fixing the Release Data (If the problem persists)

If the issue is persistent and none of the cache workarounds work, the actual release data might be the problem:

• Edit and Update a Release: Go to one of your existing releases and click Edit Release. Without making any changes, simply click Update Release. This action forces GitHub's backend to re-sync the release data, which often resolves the issue of missing releases.

Since the releases exist, using the "Edit and Update a Release" method is the most reliable way to force the server to correct the data being sent to your logged-in session.

[baijiangjie]

Hi, @Saad200724
Thank you very much for your reply. I tried all four methods in the first part several times, but none of them solved the problem. As for the second part, I couldn’t find the relevant settings (Check Release Filters). For the third part, I also tried it, but it still didn’t solve the problem..

[kyyasilmyradovv]

Hey Friend 👋

It looks like you deleted the draft releases correctly, but the old release page (like /releases/tag/v1.3.1) still appears only when you're logged in. This is almost always caused by cached release pages.

How to fix it:
++ Hard refresh the page

• Windows: Ctrl + Shift + R
• Mac: Cmd + Shift + R
  ++ Open the link in an incognito/private window (If it works there, it’s definitely a cache issue)
  ++ Clear the cache for github.com in your browser.
  ++ Re-run the delete command:
  gh release delete v1.3.1 --repo baijiangjie/CordysCRM --yes

💡 Why it happens:

• GitHub sometimes shows a cached version of release pages to logged-in users. After deletion, the public view updates first, but your logged-in view may take a bit to refresh.

[baijiangjie]

Hey @kyyasilmyradovv

Thank you for your reply. I have tried all the methods above, but none of them worked.

When I am not logged in to GitHub, the Releases page displays normally. However, once I log in with my own account, the page still fails to show the published releases.

This issue has persisted for about a week now, so I don’t think it’s likely caused by caching.

[psxvoid]

The empty releases page is already hanging for several days for my repo, hard refresh doesn't change anything for me as well (I didn't issued the gh release delete though). Setting ?page=2 works, but man, it's so annoying.

https://github.com/psxvoid/notebook-navigator/releases

[DP-Hridayan]

For my repo the releases only appear starting from Page 3.

https://github.com/DP-Hridayan/aShellYou/releases?page=3

But, in my end this is not my own caching issue, since other users are facing this same issue with my repo. I have tried editing / updating older releases but it didn't work.

Opening it in incognito mode didn't solve the issue.

The bug happened (atleast I think), when I created a draft long enough to occupy page 1 and then deleted that draft. This is just a speculation on my end!

[psxvoid]

Most likely the issue is related to draft releases and removing them manually from the GitHub UI indeed.