CDN during release
See original GitHub issueIf you got to https://katex.org right now (if you’re fast enough), you won’t see any KaTeX rendering. The CDN fails to load katex@0.13.15, presumably because jsdelivr hasn’t updated yet.
It’s probably not many minutes, but I wonder whether this could be fixed (in a stop-gap sense), e.g., by using https://cdn.jsdelivr.net/npm/katex@latest instead of https://cdn.jsdelivr.net/npm/katex@0.13.15?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
What is a CDN? How does a CDN Work? - Imperva
CDNs are the transparent backbone of the Internet in charge of content delivery. ... a CDN stores a cached version of its content...
Read more >What is a CDN? | How do CDNs work? - Cloudflare
A content delivery network (CDN) refers to a geographically distributed group of servers which work together to provide fast delivery of Internet content....
Read more >Cloud CDN release notes | Google Cloud
This page contains release notes for features and updates to Cloud CDN. You can see the latest product updates for all of Google...
Read more >What is a CDN (Content Delivery Network)? - Akamai
A content delivery network (CDN) is a group of geographically distributed servers that speed up the delivery of web content by bringing it...
Read more >Content delivery network - Wikipedia
A content delivery network, or content distribution network (CDN), is a geographically distributed network of proxy servers and their data centers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Sorry for the hassle! I think we need better ways to hold off the release.
Oops, sorry for conflicting work. Should I/you turn v0.13.15 back into a tag only, or remove the note from v0.13.16?
Edit: I see you added a note to v0.13.15, which perhaps suffices.