15308555518/ docusaurus
1
0
Fork 0
mirror of https://github.com/facebook/docusaurus.git synced 2025-12-26 01:33:02 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

misc: improve npm publishing instructions

This commit is contained in:
Alexey Pyltsyn 2020-04-27 17:09:00 +03:00
parent d90fdb04d5
commit f0d9cb26ce
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
admin/publish.md
View File

@ -14,6 +14,8 @@ If you are not currently logged into npm on your CLI, do the following:
## Docusaurus 2
<!-- TODO: describe the process of hotfix releases -->
If you're publishing new v2 versions, 2FA might get in the way as the pin might expire during the publishing as there are over 10 packages to publish. You're encouraged not to use the "Authorization and Publishing" 2FA option.
### 0. Build skeleton website with new version (Docker required)
@ -38,7 +40,7 @@ If there are no errors, you can start preparing for the new release.
Generate a GitHub auth token by going to https://github.com/settings/tokens. Save the token somewhere for future reference.
> Before running the command below, get all tags from the original repository by runnung `git fetch --tags`.
> Before running the command below, get all tags from the original repository by running `git fetch --tags`.
```sh
GITHUB_AUTH=<Your GitHub auth token> yarn changelog
@ -97,7 +99,7 @@ npm access ls-packages
</pre>
</details>
If all accesses are available, you can run the command to release a new version:
If all accesses are available, build all the necessary packages with `yarn tsc`, and then you can run the command to release a new version:
```sh
yarn lerna publish 2.0.0-alpha.41 --dist-tag next