fix: Update packages access mode #278
Merged
Conversation
This file contains 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
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.
Hi there @ivanmiletic,
Thank you for merging the previous PR! I can see that the release pipeline has failed to publish to NPM.
From what I can tell, I believe that NPM by default is assuming that the new packages are private, and since the
@gorulesnpm organisation, (I assume) is on a free plan, the upload is rejected. This pull request will set the access mode to public, which should resolve it, based on the comment on this thread.If you prefer to solve it a different way, no problem, I am eager for the new version, so created this PR to keep it moving. I've gone through older commits to the repo to see if this was an issue for the other packages initially but can't see anything - perhaps the first run was local?