-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc(v2): publish doc update after alpha.58 release #2960
Conversation
Deploy preview for docusaurus-2 ready! Built with commit c2d5f0a |
Deploy preview for docusaurus-2 ready! Built with commit aaab5b8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much! Left a comment for your consideration
@@ -99,13 +144,24 @@ npm access ls-packages | |||
</pre> | |||
</details> | |||
|
|||
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: | |||
It can happen that some accesses not granted, as an admin might add you to the @docusaurus NPM organisation, but you don't have access to the packages that are not in that organisation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to shift this portion higher up to the "Check publish rights". Feels more related there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what I thought initially, but I think these rights might not apply for the v1 release process so I let them here
publish doc update after alpha.58 release
cc @yangshun