Skip to content

Conversation

@alesblaznik
Copy link
Contributor

@alesblaznik alesblaznik commented Nov 10, 2025

This will publish binaries same time we publish to npmjs. Hope this will work now 🤞🏻... don't want to create too many incomplete releases, but CI is annoying to test.

@royaltm
Copy link
Owner

royaltm commented Nov 10, 2025

I suppose I have to make another release to test this one out? Or is there a way to redo 3.5.1? I suppose NPM will block an attempt to release the same package version, but perhaps at least the binaries will be available in the GitHub Releases.

What do you think?

@alesblaznik
Copy link
Contributor Author

I suppose I have to make another release to test this one out? Or is there a way to redo 3.5.1? I suppose NPM will block an attempt to release the same package version, but perhaps at least the binaries will be available in the GitHub Releases.

What do you think?

Good point, let's delete release and tag and then create another 3.5.1 release. Action for npmjs will fail though, but release is published there anyways. 🤞🏻

@royaltm royaltm merged commit c9f7944 into royaltm:master Nov 10, 2025
8 checks passed
@royaltm
Copy link
Owner

royaltm commented Nov 10, 2025

It worked as planned, so it seems.

Good Job @alesblaznik !

Please verify if the release works for you and thanks for the contribution!

@alesblaznik
Copy link
Contributor Author

It worked as planned, so it seems.

Good Job @alesblaznik !

Please verify if the release works for you and thanks for the contribution!

We'll bump version in our repo soon and check. Thanks for collaborating on this 🙌🏻 .

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