Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Accessing the latest version x.y.z releases by x.y or x #360

reezer opened this Issue · 14 comments

Various CDNs (Google's for example) allow access of the latest bug fix release of a certain series by not specifying the minor version number. This makes sense, because such releases usually don't contain anything that can breakage, but only contain bug, performance or stability fixes (maybe better support for certain browsers).

To give an example. The current:

should also be available as:

and once 1.8.1 is released link to:

For comparison see:

(Maybe it would be better to mention this in its own ticket, but specifying the version number twice seems unnecessary.)


So there's a few issues with implementing this:

  • It assumes everyone follows semantic versioning in the same manner
  • Depending on the Cache-Control max-age you might not actually get bug fixes for a long time (e.g. 1 year)
  • I'm not sure how we would implement this from a technical sense
    • Right now everything is just static file serving. Introducing somewhat dynamic script serving will complicate things

In regards to including the version number in the file name, my policy is to include the file exactly as it is provided by the library maintainer, filename and all, e.g.

  • Well, one should of course know the library one uses. It's also not like one would have to include such a version. (and a lot of different libraries for sanity reasons follow this or similar semantics)

  • Isn't that what ETags are for?

  • Would symlinks be an option? That way they'd implemented just like most libraries in Unix systems, which do exactly what I propose here. But I don't know if and how git supports links.


I’d also appreciate this, in my case for jQuery as well. It would be great to automatically benefit from bug fix releases (third digit) without having to monitor bug fix releases and updating paths every time.

I understand this may be complicated because it needs adjustments to the existing architecture, but I think it would make a great additional to the service.


This is most likely out of our scope for now, we are trying to keep management overheads down.

Though will keep the ticket alive if anyone has any good ideas. Symlinks sounds like the way to go but I'm not sure I want to be managing hundreds of symlinks etc


Thanks @hpatoio


In #1495 I offered to make a shell script that would manage the multitude of shell scripts and it could be added as part of your build process. @ryankirkman had a concern that any sort of complexity might not work. Have symlinks even been tried? If not, I'd be happy to give a pull request that would add symlinks for a single project to save on clutter. It appears that the CDN might just proxy the first request through to another host, so I suppose it's more important to see if the original host supports symlinks.


:+1: It will be a cool and needed feature.


Tagging in #987


:+1: nice idea ;)
whats your schedule for do it ?

@lmccart lmccart referenced this issue in processing/p5.js

CDNJS Nightly Build #260


If not wild card support, how about using "latest", especially for libs that use the npm hook - in npm there always is a latest tag. That could even promote moving to verified sources (npm) for the libs, and reduce manual submissions.


Completely agree with that, i guess having a /latest/.js and /latest/.min.js would be easier to maintain rather than using wildcards


Do you forgot this feature/issue ?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.