Automatically pull latest library versions

[cdnjs]

Automatically pull latest library versions

[thomasdavis]

It's hard to manage automatic pull request from a security perspective
unless you have any ideas?

On Tue, Dec 13, 2011 at 8:20 PM, Oliver Nightingale <
[email protected]

wrote:

Is there a smarter way to update the versions of libraries in the cdn?
You could listen for git hooks and and pull the latest releases from
GitHub, something similar to the new jQuery plugins system?

It seems this way you would always have the latest versions of projects
hosted, and then have less overhead merging pull requests.

---

Reply to this email directly or view it on GitHub:
#123

[olivernn]

I was thinking maybe people could register a github post receive hook and then cdnjs could check for new tags? I'm not sure whether this is possible though. The other option is to have the package.json file hosted in the library repositories, that way it might be more obvious when a new version is available?

I guess as long as the libraries hosted on cdnjs are always up to date its less of an issue but I know I often forget to open a new pull request when I bump the versions of the libraries I have hosted on there.

[robertcedwards]

What about using submodules in git so once the libraries are updated they can bulk updated?

[xrmx]

While having it working automagically would be cool, i've started working on a tool that looks for git tags in github repositories and compare the version with the one in package.json. The github api for retrieving the tags of repo does not list the date when the tag has been added (i can get that with another request but not handy) so in the case the tag format is a bit sloppy, eg. v1.0 vs 1.1 some parsing work is needed. Hopefully will have something to show in the next few days.

[thomasdavis]

@xrmx Sounds pretty good, looking forward to seeing it

[thomasdavis]

@ryankirkman fixing this would make management time faster, maybe if an official github link is included in the package.json we can add it to the build script. I could write this if it seems like a good idea

[ryankirkman]

@olivernn @thomasdavis I am ultra supportive of this!

If we could get library authors on board with setting up Github hooks, it
would be amazing for keeping all our libs up to date.

On Sat, Oct 13, 2012 at 7:16 PM, Thomas Davis [email protected]:

@ryankirkman https://github.com/ryankirkman fixing this would make
management time faster, maybe if an official github link is included in the
package.json we can add it to the build script. I could write this if it
seems like a good idea

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/123#issuecomment-9402363.

[thomasdavis]

Will figure something out and then encourage the community to hassle the library owners to add support.

[thomasdavis]

Activity on the repo has been increasing and a new solution for pull request might soon become a necessity. Bumped up to high priority and awaiting further ideas!

An npm-like tool for cdnjs for library authors seems like a good idea so far to me. And then developers can just lobby against authors.

[petecooper]

On the grounds that npm updating is now in place, has a schedule and seems to be working, I am pretty sure this issue can be closed. Any objections, @thomasdavis or @ryankirkman? How about you, @olivernn - is your issue covered by the nom auto-updating? Thanks, all.

[ryankirkman]

I'm happy to close this issue.

On Saturday, February 1, 2014, Pete Cooper [email protected] wrote:

On the grounds that npm updating is now in place, has a schedule and seems
to be working, I am pretty sure this issue can be closed. Any objections,
@thomasdavis https://github.com/thomasdavis or @ryankirkmanhttps://github.com/ryankirkman?
How about you, @olivernn https://github.com/olivernn - is your issue
covered by the nom auto-updating? Thanks, all.

Reply to this email directly or view it on GitHubhttps://github.com//issues/123#issuecomment-33875901
.