Skip to content

chore(crc32c): set publishConfig.access to public #207

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

Merged
merged 2 commits into from
Aug 23, 2021

Conversation

alex-chew
Copy link
Contributor

When running lerna publish to publish a new scoped package, if
publishConfig.access is unset, then the package is published with
private visibility ("restricted") by default [1]. Since this package is
intended for public consumption, we should configure this property
accordingly.

[1] https://github.com/lerna/lerna/tree/main/commands/publish#publishconfigaccess

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

When running `lerna publish` to publish a new scoped package, if
`publishConfig.access` is unset, then the package is published with
private visibility ("restricted") by default [1]. Since these packages
are intended for public consumption, we should configure this property
accordingly.

[1] https://github.com/lerna/lerna/tree/main/commands/publish#publishconfigaccess
@alex-chew alex-chew requested a review from seebees August 12, 2021 20:36
@alex-chew alex-chew merged commit e4e9826 into aws:master Aug 23, 2021
@alex-chew alex-chew deleted the publish-config-access-public-crc32c branch August 23, 2021 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants