However, when releasing Git for Windows v2.42.0 this was not so. I had to mark it as "latest" manually, and I only realized this because the gitforwindows.org update would fail (because it would still pick up v2.41.0(3) as the latest release).
Let's just make it explicit that we want to mark it as the latest version (at least as long as we're not publishing a pre-release).
According to the REST API documentation of
create-a-release
, themake_latest
should default totrue
.However, when releasing Git for Windows v2.42.0 this was not so. I had to mark it as "latest" manually, and I only realized this because the
gitforwindows.org
update would fail (because it would still pick up v2.41.0(3) as the latest release).Let's just make it explicit that we want to mark it as the latest version (at least as long as we're not publishing a pre-release).