ci: set npm packages to public after publish#4154
Closed
kentkwu wants to merge 1 commit intoapache:mainfrom
Closed
ci: set npm packages to public after publish#4154kentkwu wants to merge 1 commit intoapache:mainfrom
kentkwu wants to merge 1 commit intoapache:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gemfury appears to not respect the
--access publicflag on initial publish.Combined with the issue addressed in #4144, this means that each nightly publish reverts the packages to private which then requires a manual fix.
This PR applies a fix to make another pass to set all npm packages to public after publishing