Skip to content

Conversation

@piwysocki
Copy link
Contributor

No description provided.

@piwysocki piwysocki requested a review from a team as a code owner December 20, 2022 06:51
@mkuthan
Copy link
Member

mkuthan commented Dec 20, 2022

@adrianmroz-allegro, @piter75 - do you remember why we pinned release-it to the specific version? I'm almost sure that we have found a bug in release-it and decided to stay with the old version.

@adrianmroz-allegro
Copy link
Contributor

We pinned this version because newer didn't work with our bamboo action (yeah, long time ago) for releasing consecutive beta versions. Probably releasing new beta with this changes would be enough for a test.

@piwysocki
Copy link
Contributor Author

Is it not better to install latest 15?

npm install -g release-it@15

@piter75
Copy link
Contributor

piter75 commented Jan 11, 2023

we have found a bug in release-it and decided to stay with the old version

newer didn't work (...) for releasing consecutive beta versions

The issue was discovered in release-it v14.0.x and we pinned its version at v13.7.1 then.
We are using v14.6.1 now so the issue must have been fixed in the meantime and the change to a full version was probably simply mechanical ;-)

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.

4 participants