3 ms·
On any release - which means a tag containing the version number - I first check the latest version number in the changelog/release notes against the version nu
by ReleaseCandidat 3y ago
On any release - which means a tag containing the version number - I first check the latest version number in the changelog/release notes against the version number in the tag and if they aren't the same CI throws an error.
If the versions match, the latest changelog/release notes are also extracted and used as the release text (for example on GitHub or sending internal emails or wherever the release information is needed).
- myrmidon 3y agoSeconding this. Sounds trivial and stupid but just having an an automated check for a corresponding changelog entry before acutally versioning/releasing is a huge improvement. If the release management/tagging is often done from developer machines instead of happening in/via CI, I'd also advise checking for a clean worktree (no uncomitted changes) before allowing a release.
- ReleaseCandidat 3y ago> I'd also advise checking for a clean worktree (no uncomitted changes) before allowing a release Oh yes, this had been a source of problems for us in the past too.