Travis GitHub Releases

[simonbrunel]

Update .travis.yml to build and upload dist/* files (and a ZIP archive) when a tag is created (proof of concept), then remove dist/* files from the repository. Also update links to the documentations and README.md.

The new release process would be:

• draft a release (optional)
• change the package.json version
• create the associated git tag and push it on GitHub
• a build is triggered by Travis for this tag (automatic)
• generated dist/* files are uploaded along the release (automatic)
• npm package is published to npmjs (automatic)

We will also need to update CDNjs to use these uploaded files.

The ZIP archive contains the following files:

/samples/**/*
/Chart.bundle.js
/Chart.bundle.min.js
/Chart.js
/Chart.min.js
/LICENSE.md

The release attached files will be:

Chart.bundle.js
Chart.bundle.min.js
Chart.js
Chart.min.js
Chart.js.zip
Source code (zip)
Source code (tar.gz)

See original PR #2550 & #2552 and issue #2554

[simonbrunel]

@etimberg, @tannerlinsley: I wrote a gulp task to create a Chart.js.zip package, which one will be deployed by Travis. It's very similar to the current zip file containing the whole repository, but only for samples.

We could also provide only the Chart.js.zip file (no individual js files)?

Note: users who download the repo (source) would have to gulp build before using samples, which seems pretty normal, right?

[simonbrunel]

Travis should now release the npm package automatically (2f28aed). When releasing a new version, we should updated the package.json version before pushing the new tag. I updated the PR description (release process).

[simonbrunel]

Added the .npmignore, so hopefully the npm release should include exactly the same files as before. I'm thinking that now we might want to ignore more files for the npm package, what do you think?

[etimberg]

Is there enough consensus to merge this?

[simonbrunel]

@zachpanz88 @tannerlinsley @nnnick ^^

[panzarino]

+1

[fulldecent]

How can we confirm the API secure key works, or is there anything else we need to do to accept this PR?

Also, can you please provide documentation that pushing tags triggers a new Travis CI build?

[etimberg]

@fulldecent we tried out a similar process in the color lib https://github.com/chartjs/chartjs-color/blob/master/.travis.yml

[panzarino]

It definitely works, I would encourage a merge soon.

[etimberg]

Yeah. I think we should merge this

[fulldecent]

+1

[fulldecent]

I just read up on the documentation at https://docs.travis-ci.com/user/deployment/releases on why this works. Ready to merge, perhaps one more set of eyes can look at this. @tannerlinsley @nnnick @simonbrunel @zachpanz88

[simonbrunel]

@fulldecent: same process as Chart.Deferred.js, except for deploying to npm. I'm confident that everything will run smoothly, but if not, we can still publish manually until we adjust the process (I tried to keep commits well documented and consistent, please don't squash on merge).

The only missing part is CDNjs: we should update the package.json on their repo to reflect these changes before the next release. I don't think they support autoupdate from GitHub release files so it should now use npm release (which is the recommended method). I will prepare a PR if everyone is agree to merge that one.

[etimberg]

Ok, let's merge this and then @simonbrunel can update CDNjs