Skip to content

Latest commit

 

History

History
31 lines (18 loc) · 2.32 KB

publishing.md

File metadata and controls

31 lines (18 loc) · 2.32 KB
Raw

Publishing a new version of mdn-browser-compat-data

Project owners publish new releases of mdn-browser-compat-data on npm. MDN staff deploy the package to the MDN site. Usually, this happens every Thursday (MDN never deploys to production on Fridays).

Any owner can complete the following steps to publish a new version, but please coordinate releases with Florian Scholz.

To create and publish a new version of mdn-browser-compat-data:

  1. Figure out the new version number by looking at past releases. If the release is a non-breaking and data-only update, we're using patch versions. Lets assume that's the case and the next version should be 1.0.3.

  2. On your updated and clean master branch, run npm version patch -m "Patch release containing data or non-breaking updates only". Locally, this updates package.json, creates a new commit, and creates a new release tag (see also the docs for npm version).

  3. Push the commit to master: git push origin master.

  4. Check if the commit passes fine on Travis CI.

  5. If Travis is alright, push the git tag as well: git push origin v1.0.3. This step will trigger Travis to publish to npm automatically (see our .travis.yml file).

  6. Check Travis CI again for the v1.0.3 build and also check mdn-browser-compat-data on npm to see if 1.0.3 shows up correctly once Travis has finished its work.

  7. Notify the #mdn-dev IRC channel on Mozilla Slack about the new release.

  8. Create a new release on GitHub by running npm run release-notes -- v1.0.3).

  9. Update tracking issues:

    • #6369 for every release, update with the results of npm run stats api
    • #3555 when there's significant progress, update with the results of npm run stats