You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although we use automatic semantic release versioning, in rare cases we need to also create manual releases on GitHub. The combination has worked properly so far, but with the latest automated release 3.1.26 we are suddenly missing the previous version 3.1.25 in CHANGELOG.md. This previous version 3.1.25 had been created manually on GitHub, but it was detected correctly when release 3.1.26 was being created by semantic release (s. log below):
Although we use automatic semantic release versioning, in rare cases we need to also create manual releases on GitHub. The combination has worked properly so far, but with the latest automated release 3.1.26 we are suddenly missing the previous version 3.1.25 in CHANGELOG.md. This previous version 3.1.25 had been created manually on GitHub, but it was detected correctly when release 3.1.26 was being created by semantic release (s. log below):
semantic-release:release-notes-generator previousTag: 'v3.1.25'
semantic-release:release-notes-generator currentTag: 'v3.1.26'
We expect to have this in CHANGELOG.md:
3.1.26
3.1.25
1.0.1
But we have this:
3.1.26
1.0.1
Is there anything that we should take into account when creating manual releases?
The text was updated successfully, but these errors were encountered: