Skip to content

version 0.3.15 #392

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

Merged
merged 1 commit into from
Jan 7, 2025
Merged

version 0.3.15 #392

merged 1 commit into from
Jan 7, 2025

Conversation

antonsviridov-src
Copy link
Contributor

Tagged release failed, so updating version manually (I deleted the tag and will re-create after this PR)

Test plan

N/A

Copy link
Contributor

@varungandhi-src varungandhi-src left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this didn't publish anything, so this is OK. However, the current CI setup has the unfortunate potential failure mode where you can publish the NPM package successfully, and then fail to publish the Docker image. In that case, deleting the tag + recreating it increases the risk of confusion.

It might be simpler to instead always treat tags as immutable (including for releases which failed to publish), and simply document them as failed in the CHANGELOG.

@antonsviridov-src
Copy link
Contributor Author

In that case, deleting the tag + recreating it increases the risk of confusion.

Yes, that's the only reason I deleted the tag – because nothing was published.
Agree with treating the tags as immutable.

@antonsviridov-src antonsviridov-src merged commit 1b2bf90 into main Jan 7, 2025
7 checks passed
@antonsviridov-src antonsviridov-src deleted the version-0.3.15 branch January 7, 2025 13:53
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