Skip to content
This repository was archived by the owner on Jul 15, 2023. It is now read-only.

Releases.md

Latest commit

 

History

History
40 lines (28 loc) · 1.67 KB

Releases.md

File metadata and controls

40 lines (28 loc) · 1.67 KB

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 minor version and push

Publish the npm package

Package should be published only from dist/build folder.

  • For beta release run npm publish --tag beta

  • For stable release run npm publish

If you need to promote package from beta to stable use npm dist-tag add tslint-microsoft-contrib@<version> latest