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

[CI] Don't publish NPM versions if they already exist. #177

Open
sammarks opened this issue Jul 5, 2022 · 1 comment
Open

[CI] Don't publish NPM versions if they already exist. #177

sammarks opened this issue Jul 5, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@sammarks
Copy link
Collaborator

sammarks commented Jul 5, 2022

Just a mental note for me to remember to do this; it's cumbersome having to create new versions when debugging releases (like Flutter) simply to avoid the error we get when publishing over an existing NPM package version.

Just need to skip that publish step if the version already exists.

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@sammarks sammarks added the enhancement New feature or request label Jul 5, 2022
@sammarks sammarks self-assigned this Jul 5, 2022
@sammarks
Copy link
Collaborator Author

Brute-force solution implemented currently, where we just ignore the publish step if it fails. Obviously, not a great solution, but for the purposes of getting the website up and running, it works :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant