Skip to content
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

fix(docs): update npm-publish access flag info #3630

Merged
merged 1 commit into from Aug 11, 2021

Conversation

austincho
Copy link
Contributor

The only way to turn a public package that's been published to private (or vice versa) is to use npm access Using the access flag on the npm publish command after the initial publish, has no effect on the access level. The documentation on npm-publish should note these characteristics.

References

Closes #1341

@austincho austincho requested a review from a team as a code owner August 8, 2021 17:58
@darcyclarke darcyclarke added semver:patch semver patch level for changes Release 7.x work is associated with a specific npm 7 release labels Aug 9, 2021
@darcyclarke darcyclarke added this to the OSS - Sprint 35 milestone Aug 9, 2021
@wraithgar wraithgar merged commit d1812f1 into npm:release-next Aug 11, 2021
@wraithgar
Copy link
Member

Thanks for submitting this. docs are a very important part of the cli and improvements here are very much appreciated.

@wraithgar wraithgar mentioned this pull request Aug 12, 2021
@wraithgar
Copy link
Member

Sorry about this, but when I accepted this I didn't realize it was in the auto-generated portion of these docs. We're gonna have to revert this and find a better place to put this.

@wraithgar
Copy link
Member

This is where we'd want to make the change

description: `

isaacs added a commit that referenced this pull request Aug 16, 2021
This should prevent the kind of thing we've seen where people edit the
generated docs, as in #3654 and #3630, and provide them with a helpful
pointer so they put the config documentation changes in the right place.
isaacs added a commit that referenced this pull request Aug 16, 2021
This should prevent the kind of thing we've seen where people edit the
generated docs, as in #3654 and #3630, and provide them with a helpful
pointer so they put the config documentation changes in the right place.
isaacs added a commit that referenced this pull request Aug 16, 2021
When we accidentally edit the auto-generated portions of the docs, this
will catch the error and cause CI to fail.

Later phase automated safety check that the early-stage human commenting
in the last commit also addresses.

Re: #3654
Re: #3630
wraithgar pushed a commit that referenced this pull request Aug 17, 2021
This should prevent the kind of thing we've seen where people edit the
generated docs, as in #3654 and #3630, and provide them with a helpful
pointer so they put the config documentation changes in the right place.
wraithgar pushed a commit that referenced this pull request Aug 17, 2021
When we accidentally edit the auto-generated portions of the docs, this
will catch the error and cause CI to fail.

Later phase automated safety check that the early-stage human commenting
in the last commit also addresses.

Re: #3654
Re: #3630

PR-URL: #3655
Credit: @isaacs
Close: #3655
Reviewed-by: @nlf
isaacs added a commit that referenced this pull request Aug 17, 2021
This should prevent the kind of thing we've seen where people edit the
generated docs, as in #3654 and #3630, and provide them with a helpful
pointer so they put the config documentation changes in the right place.
isaacs added a commit that referenced this pull request Aug 17, 2021
When we accidentally edit the auto-generated portions of the docs, this
will catch the error and cause CI to fail.

Later phase automated safety check that the early-stage human commenting
in the last commit also addresses.

Re: #3654
Re: #3630
isaacs pushed a commit that referenced this pull request Aug 19, 2021
PR-URL: #3630
Credit: @austincho
Close: #3630
Reviewed-by: @wraithgar

EDIT(@isaacs): rebased and edited to put config documentation in the
correct location.
@wraithgar wraithgar mentioned this pull request Aug 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release 7.x work is associated with a specific npm 7 release semver:patch semver patch level for changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants