FEX submission not updating to new release on GitHub

12 views (last 30 days)
I created a new release on GitHub not quite 24h ago, but the FEX page is still stuck on the prior release. I don't know if these delays are occasionally very long, but the site suggests "up to an hour", so I elect to assume that as the norm.
I do occasionally get email notifications when I update that falsely say that the update couldn't be performed because the new version number is less than the old version number. Not that those emails were ever correct, but I checked anyway and haven't recieved any notifications that would indicate a problem.
So, is it plausible that it's just slow? Is there a way to provoke an update?

Accepted Answer

DGM
DGM on 10 Jul 2023
After three days, I ended up just editing the FEX page and selecting "Change Repository" and setting it to the same repository again, at which point the FEX page immediately refreshed with the new version.
What's strange is the Version History section now indicates that it picked up the new version 2 days ago, despite the fact that it never actually showed up in either browser until I forced a change to page. Maybe it did and somehow both my browsers were stuck on a cached version of the page? I doubt that, but either way, bumping the repo link fixed it.
  1 Comment
Bruno Mattos
Bruno Mattos on 15 Jul 2023
I had the same problem. It only found the new release after I reentered the link to the github repo.

Sign in to comment.

More Answers (0)

Categories

Find more on File Operations in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!