You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Libraries not being updated to latest versions #14263
Originally posted by heyesr September 29, 2024
Hi there,
I've just released a new version of my software - RGraph 6.19 - but CDNjs doesn't appear to be picking up the new release. The Git Repository is tagged - https://github.com/heyesr/rgraph/tree/6.19 (and branched at this tag too fwiw) but so far nada. Do I just need to be more patient for CDNjs to mirror the file?
Hey folks, good news! We've got the new auto-update automation up and running, and you can see it starting to work through the backlog of library versions over in https://github.com/cdnjs/logs
Obviously, it is going to take quite a while for it to get through everything that has been missed over the last year or so, and there's a good chance we might need to pause it if/when we encounter any teething issues. I asked that you have some patience as it does its thing. Please do shout if you see any issues with the versions that it has processed!
cdnjs does not seem to be updating any libraries, and this appears to have been the case for three or so weeks. I informally escalated this last weekend to no avail, this has now been formally escalated to Cloudflare in #01220256
FYI #14261 which is tracking this repository not syncing the updates from the CDN (not that there are many updates to sync as updating itself has been broken for a while too, per this issue).
@xtuc put in place a fix to allow new versions to be processed again ❤️ I believe there were a couple of versions that got partially processed as it broke, which will need to be re-processed. Once those are rectified, I'll close out this issue.
Chart.js version 4.4.6 was released on October the 28. That is 2 weeks after the issue should be fixed but I don't see the version on the CDN. So is there still an issue or is something else the culprit of this?
Hey folks, good news! We've got the new auto-update automation up and running, and you can see it starting to work through the backlog of library versions over in https://github.com/cdnjs/logs
Obviously, it is going to take quite a while for it to get through everything that has been missed over the last year or so, and there's a good chance we might need to pause it if/when we encounter any teething issues. I asked that you have some patience as it does its thing. Please do shout if you see any issues with the versions that it has processed!
Reacted by Richard, Shuqiao Zhang and Chaos
Reacted by Martin Costello, Justin Keller, Heptazhou, Ruoyu Zhong, Simona Badoiu, Gerych1984, Paul Meserve, Joe Tiedeman, Chaos, Bhao and 2 more
Reacted by Shuqiao Zhang, Chaos, Bhao and Ian Gilman
No worries. I should be clear that much of this is very much a royal we, I'm just the one providing updates here, the folks at Cloudflare are the ones that've put in all the hard work to rewrite the automation. I'm sure there'll be more info shared by them in due course about this.
This is great, thank you so, so much for the update Matt. So this should mean that once the automation has caught up, the API for cdnjs etc will start reporting out the latest versions? For my purposes getting libraries, versions and hashes from the API is more than sufficient, the repo itself being synced is less of a concern for me.
Please pass on mine and others thanks to the folks at Cloudflare for making progress on this. It's massively appreciated.
All your previous versions released many years ago have been picked up by cdnjs just fine -- looks like we're just missing the most recent version published a day ago. I suspect the bot is still catching up from when it was re-enabled, but if we don't pick up the new version in the next few days, let me know and we can dig further.
On Tue, 28 Jul 2026, Matt Cowley wrote:
MattIPv4 left a comment (cdnjs/cdnjs#14263)
(why not IPv6?)
All your previous versions released many years ago have been picked up
by cdnjs just fine -- looks like we're just missing the most recent
version published a day ago. I suspect the bot is still catching up
from when it was re-enabled, but if we don't pick up the new version in
the next few days, let me know and we can dig further.
@simonabadoiu can you take a look at why the bot isn't picking up that version, given it has been published for a month? Is there any further diagnosis I can do from the outside?
@simonabadoiu can you take a look at why the bot isn't picking up that version, given it has been published for a month? Is there any further diagnosis I can do from the outside?
10.9.8 was published on 2026-08-04, after 11.16.0 and 26 minutes after 11.16.1. It was picked up on 2026-08-13, but 11.16.0 and 11.16.1 were not.
mermaid-layout-elk was released alongside 11.16.0, 11.17.0 and 12.0.0. Its matching versions (0.2.2, 0.2.3, 1.0.0) are all on cdnjs; the last one was picked up on 2026-09-16.
Possible cause: from 11.16.0 on, the fileMap matches 1,167–1,315 files per version, up from 884 in 11.15.0. Going by the logs, the largest version the new bot has published since mid-June is rxdb 17.5.0, with 1,096 files. Total size seems less likely to be the cause: 11.16.x/11.17.x match about 80 MiB of files, and duckdb-wasm versions matching about 113 MiB have gone through. Could the bot be hitting a per-version file-count limit, or something else that grows with the number of files?
Activity
MattIPv4 commentedon Sep 29, 2024
👀 @xtuc looks like the new version was detected, but wasn't actually processed? https://github.com/cdnjs/logs/tree/prod/packages/R/RGraph/6.19
MattIPv4 commentedon Oct 6, 2024
cdnjs does not seem to be updating any libraries, and this appears to have been the case for three or so weeks. I informally escalated this last weekend to no avail, this has now been formally escalated to Cloudflare in #01220256
FYI #14261 which is tracking this repository not syncing the updates from the CDN (not that there are many updates to sync as updating itself has been broken for a while too, per this issue).
limzykenneth commentedon Oct 11, 2024
Not sure if it has recovered but the latest release of p5.js (1.11.0) seems to be available now: https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.11.0/p5.min.js.
It was released about 2 weeks ago and we have noticed at the time it didn't update on CDNjs (stuck on 1.10.0).
heyesr commentedon Oct 11, 2024
Yes, the latest version of RGraph (6.19, https://cdnjs.com/libraries/RGraph/6.19) is available too. Thanks very much for the help!
gunjandatta commentedon Oct 11, 2024
The latest is working for the gd-sprest library too. Thanks for the help.
MattIPv4 commentedon Oct 14, 2024
@xtuc put in place a fix to allow new versions to be processed again ❤️ I believe there were a couple of versions that got partially processed as it broke, which will need to be re-processed. Once those are rectified, I'll close out this issue.
LeeLenaleee commentedon Nov 21, 2024
Chart.js version 4.4.6 was released on October the 28. That is 2 weeks after the issue should be fixed but I don't see the version on the CDN. So is there still an issue or is something else the culprit of this?
https://github.com/chartjs/Chart.js/releases/tag/v4.4.6
https://cdnjs.com/libraries/Chart.js
https://www.npmjs.com/package/chart.js?activeTab=versions
EDIT:
Chart.js v4.4.7 released 6 days ago and is also not being picked up by cdnjs
evannotfound commentedon Dec 3, 2024
Same here for Hexo theme redefine v2.8.2 https://github.com/EvanNotFound/hexo-theme-redefine/tree/v2.8.2
echolet commentedon Dec 7, 2024
https://cdnjs.com/libraries/quill/2.0.3 shows no files
gunjandatta commentedon Jan 21, 2025
It stopped working again.
lucaswerkmeister commentedon Feb 7, 2025
https://cdnjs.com/libraries/codex is also missing the latest version (which should be 1.20.1, compare @wikimedia/codex on npm). The logs repo has a 1.20.0 directory, but with fewer files than the 1.19.1 directory; meanwhile, the cdnjs repo only goes up to 1.12.0.
47 remaining items
MattIPv4 commentedon Jun 23, 2026
Hey folks, good news! We've got the new auto-update automation up and running, and you can see it starting to work through the backlog of library versions over in https://github.com/cdnjs/logs
Obviously, it is going to take quite a while for it to get through everything that has been missed over the last year or so, and there's a good chance we might need to pause it if/when we encounter any teething issues. I asked that you have some patience as it does its thing. Please do shout if you see any issues with the versions that it has processed!
nodesocket commentedon Jun 23, 2026
@MattIPv4 awesome, thanks for staying on top of this and getting over the finish line 🏁 . Appreciated 🙏🏻
MattIPv4 commentedon Jun 23, 2026
No worries. I should be clear that much of this is very much a royal we, I'm just the one providing updates here, the folks at Cloudflare are the ones that've put in all the hard work to rewrite the automation. I'm sure there'll be more info shared by them in due course about this.
heyesr commentedon Jun 24, 2026
Congrats and thanks for the update! :-)
milkyjoe90 commentedon Jun 25, 2026
This is great, thank you so, so much for the update Matt. So this should mean that once the automation has caught up, the API for cdnjs etc will start reporting out the latest versions? For my purposes getting libraries, versions and hashes from the API is more than sufficient, the repo itself being synced is less of a concern for me.
Please pass on mine and others thanks to the folks at Cloudflare for making progress on this. It's massively appreciated.
MattIPv4 commentedon Jun 28, 2026
Indeed, as the bot starts processing new versions they'll show up on the API.
mirabilos commentedon Jul 28, 2026
same happens for me (dygraphs) every time I release it, unpkg picks it up almost immediately
MattIPv4 commentedon Jul 28, 2026
https://github.com/cdnjs/logs/tree/prod/packages/d/dygraph
https://github.com/cdnjs/packages/blob/master/packages/d/dygraph.json
https://www.npmjs.com/package/dygraphs?activeTab=versions
All your previous versions released many years ago have been picked up by cdnjs just fine -- looks like we're just missing the most recent version published a day ago. I suspect the bot is still catching up from when it was re-enabled, but if we don't pick up the new version in the next few days, let me know and we can dig further.
mirabilos commentedon Jul 28, 2026
add jsDelivr as third CDN alternative
vndroid commentedon Sep 6, 2026
highlight.jsseems that there has been no update.MattIPv4 commentedon Sep 12, 2026
@vndroid
highlight.jswas last updated a month ago for the11.11.2release: https://github.com/cdnjs/logs/tree/prod/packages/h/highlight.jsLooking at the config for the package (https://github.com/cdnjs/packages/blob/master/packages/h/highlight.js.json), it is set to pull from https://www.npmjs.com/package/@highlightjs/cdn-assets, which does have a newer
11.12.0release that we haven't picked up even though the file map appears to still match.@simonabadoiu can you take a look at why the bot isn't picking up that version, given it has been published for a month? Is there any further diagnosis I can do from the outside?
vndroid commentedon Sep 14, 2026
By the way, the mathjax , font-awesome and tocbot could not be found.
Snrat commentedon Sep 26, 2026
mermaid is stuck at 11.15.0 on cdnjs. None of the six releases since then have been picked up:
11.16.0 (2026-06-25), 11.16.1 (2026-08-04), 11.17.0 (2026-08-19), 11.17.1 (2026-08-24), 11.17.2 (2026-08-25), 12.0.0 (2026-09-10, current
latest)mermaid, fileMapdist/**/!(*.html). The fileMap still matches the new releases, anddist/mermaid.min.jsis in all of them.This doesn't look like the backlog:
mermaid-layout-elkwas released alongside 11.16.0, 11.17.0 and 12.0.0. Its matching versions (0.2.2, 0.2.3, 1.0.0) are all on cdnjs; the last one was picked up on 2026-09-16.Possible cause: from 11.16.0 on, the fileMap matches 1,167–1,315 files per version, up from 884 in 11.15.0. Going by the logs, the largest version the new bot has published since mid-June is rxdb 17.5.0, with 1,096 files. Total size seems less likely to be the cause: 11.16.x/11.17.x match about 80 MiB of files, and duckdb-wasm versions matching about 113 MiB have gone through. Could the bot be hitting a per-version file-count limit, or something else that grows with the number of files?