Releases

Overview

• The npm package is published by the Microsoft account
• Directions for publishing with the Microsoft Account are available with CORPNET access
• Releases are made from the "master" branch and tagged with the format "[version]"

Prepare the tslint-microsoft-contrib master branch

• Make sure there are 0 closed issues without a milestone. Assign milestone as needed using this query
• Close the milestone
• Open the next milestone
• Update CHANGELOG.md. Stable releases should contain list of new changes as well as full list of changes since previous stable release.
• Make sure package.json and package-lock.json contain the version you wish to publish
• Update README.md to have the correct links and version numbers for new rules (replace @next placeholder with next version)
• Pull any recent git changes and rebuild:

git pull
npm run test

• Tag the master branch with the format [version]

git tag 0.0.1
git push --tags

• Create release for newly pushed tag
• Increase the version number in package.json and README.md to the next patch version and push

Prepare the tslint-microsoft-contrib releases branch

• Clone the repo again to a new folder:

git clone https://github.com/Microsoft/tslint-microsoft-contrib tslint-microsoft-contrib-releases

• Checkout branch releases

git checkout releases

• Replace all files with the contents of /dist/build directory created from master
• Commit and push to remote
• Tag the releases branch with the format npm-[version]

git tag npm-2.0.10
git push --tags

Publish the Package

Run publishing from the releases branch as well.

If this is a beta package, use:

npm publish --tag beta

If this is not, use:

npm publish