This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 198
Releases
Josh Goldberg edited this page Aug 6, 2018
·
24 revisions
- 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]"
- The npm packages are pushed to the "releases" branch and tagged with the format "npm-[version]"
- 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 the Release Notes
- Make sure package.json and package-lock.json contain the version you which to publish
- Update README.md to have the correct version numbers and links
- Pull any recent git changes:
git pull
- Tag the master branch with the format [version]
git tag 0.0.1
git push --tags
- 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
- Go back to the master branch, increase the version number in package.json and README.md, and push
- Follow the steps at https://opensourcehub.microsoft.com/articles/how-to-publish-npm-package
- Basically just send the email they want and wait a little while
- Include the npmjs.org user ids of all contributors: brndkfr, hamletdrc, dmanesku