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.

Sign up for GitHub

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

Jump to bottom

fix: add not published check #113

Merged
merged 1 commit into from
May 11, 2022
Merged

fix: add not published check #113

merged 1 commit into from
May 11, 2022

Conversation

ianlnf
Copy link
Contributor

@ianlnf ianlnf commented May 11, 2022

  • Sets allow publish if not published (404) error returned from npm view --json

resolves #110

simoneb
simoneb reviewed May 11, 2022
View reviewed changes
test/publishToNpm.test.js Show resolved Hide resolved
test/publishToNpm.test.js Show resolved Hide resolved
@simoneb simoneb merged commit 27430b2 into main May 11, 2022
@simoneb simoneb deleted the fix/110-publish-package-not-exist branch May 11, 2022 11:49
@optic-release-automation optic-release-automation bot mentioned this pull request May 11, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@simoneb simoneb simoneb approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

First release of a package on npm does not work
2 participants
@ianlnf @simoneb