caleb-brown/unity-atoms
1
0
Fork 0
mirror of https://github.com/unity-atoms/unity-atoms.git synced 2025-01-22 08:08:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity
canary
unity-atoms/PUBLISHING.md
Adam Ramberg 50d04f1c9e Add a last step to PUBLISHING.md
2023-08-04 23:41:57 +02:00

1.2 KiB
Raw Permalink Blame History

Publishing

Here is a check list for publishing a new version:

  • [] Checkout the canary branch and make sure CHANGELOG.md is up to date.
  • [] Update the version number in all package.json files (on the root and in all the Packages/<PackageName>/package.json)
  • [] Update the root README.md file with the correct version. Also update the version in docs/introduction/installation.md.
  • [] Commit and push your changes to the canary branch.
  • [] Merge the canary branch into the master branch.
  • [] Publish a new version of the website.
    • [] Go (via the terminal) to the website folder.
    • [] Run npm start to test and see that it runs as expected.
    • [] Run GIT_USER=<your-username> \ CURRENT_BRANCH=master \ npm run publish-gh-pages to publish the website.
  • [] Create a new release under releases on the Github repo.
  • [] From the root run npm run publish:all. This is only possible for me (Adam Ramberg) at the moment. Will need to look into a solution for this.
  • [] If master and canary have deviated, then checkout canary, run git reset --hard master and force push in order to make them idenctical. This ensures that the work on the next release can start from a clean slate.