From f439d9fce390cbb6a720a6712b43075ceb1f0241 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emanuel=20Tesa=C5=99?= Date: Fri, 9 Dec 2022 19:11:38 +0100 Subject: [PATCH] Fix publish (#35) * v2.0.2 * v2.0.3 * Fix publish --- .DS_Store | Bin 6148 -> 6148 bytes README.md | 17 +- docs/index.html | 13 +- package.json | 14 +- yarn.lock | 1496 +---------------------------------------------- 5 files changed, 34 insertions(+), 1506 deletions(-) diff --git a/.DS_Store b/.DS_Store index ca2b7874ee44cef1857d5487e8c8184223131c55..d09f88fcdc77a9766cb19b2e801b6a0fe3b074bd 100644 GIT binary patch delta 257 zcmZoMXfc=|#>B`mu~3YagMono$PnRV0y02=bz;D7M%IZs()H{N1q_J{$qd;*GMypS zGbcYeDJMS(s73&Y`9b(U6ad+rsHzzh7>r2QQ5Ia3my@5D4m6L^2&AjHu~3+iaWW61G$#`S1Tanv*uD7!qd42-4~$PYvvcrs0F`Zi$oQRk YGQWr-CnHc*0!Za#6CUNwF(NCN0iE0tZU6uP diff --git a/README.md b/README.md index 0df4a08..3b31028 100644 --- a/README.md +++ b/README.md @@ -119,11 +119,12 @@ contribute just follow these steps: ## Publishing -To publish run: - -```sh -# This needs to be run with "npm run" and not "yarn" -# See: https://github.com/sindresorhus/np/issues/432#issuecomment-583732143 -# We could set the publishConfig correctly, but using NPM is good enough -npm run publish-new-version -``` +To release a new version follow these steps: + +1. `git checkout master && git pull` - ensure you are on the "master" branch with latest changes +2. `yarn version` - choose "x.y.z" as the version to be released +3. `git show` - verify the changes of the version commit +4. `yarn build` - only build the package after the "yarn version" command so the bundled + "package.json" uses the updated version +5. `yarn publish --access public` +6. `git push --follow-tags` - to push the commits to a "main" branch diff --git a/docs/index.html b/docs/index.html index f134a43..99902bd 100644 --- a/docs/index.html +++ b/docs/index.html @@ -123,9 +123,16 @@

Contribution

Publishing

-

To publish run:

-
# This needs to be run with "npm run" and not "yarn"
# See: https://github.com/sindresorhus/np/issues/432#issuecomment-583732143
# We could set the publishConfig correctly, but using NPM is good enough
npm run publish-new-version -
+

To release a new version follow these steps:

+
    +
  1. git checkout master && git pull - ensure you are on the "master" branch with latest changes
  2. +
  3. yarn version - choose "x.y.z" as the version to be released
  4. +
  5. git show - verify the changes of the version commit
  6. +
  7. yarn build - only build the package after the "yarn version" command so the bundled +"package.json" uses the updated version
  8. +
  9. yarn publish --access public
  10. +
  11. git push --follow-tags - to push the commits to a "main" branch
  12. +