Maintaining

Release Process

Chart.js relies on Travis CI to automate the library releases.

Releasing a New Version

1. draft release notes on GitHub for the upcoming tag
2. update master package.json version using semver semantic
3. merge master into the release branch
4. follow the build process on Travis CI

Note: if master is merged in release with a package.json version that already exists, the tag creation fails and the release process is aborted.

Automated Tasks

Merging into the release branch kicks off the automated release process:

• build of the dist/*.js files
• bower.json is generated from package.json
• dist/*.js and bower.json are added to a detached branch
• a tag is created from the package.json version
• tag (with dist files) is pushed to GitHub

Creation of this tag triggers a new build:

• Chart.js.zip package is generated, containing dist files and examples
• dist/*.js and Chart.js.zip are attached to the GitHub release (downloads)
• a new npm package is published on npmjs

Finally, cdnjs is automatically updated from the npm release.

Further Reading

• Travis GitHub releases
• Bower support and dist/* files
• cdnjs npm auto update