Skip to content

Commit 8d66606

Browse files
committed
release: explicitly mark full releases as the latest release
According to the REST API documentation at https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#create-a-release the `make_latest` should default to `true`. 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). Signed-off-by: Johannes Schindelin <[email protected]>
1 parent 82166f3 commit 8d66606

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

.github/actions/github-release/action.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,14 +138,16 @@ runs:
138138
await state.refreshToken()
139139
140140
console.log('Publishing release')
141+
const isPrerelease = '${{ inputs.tag-name }}'.indexOf('-rc') > 0
141142
await updateRelease(
142143
console,
143144
state.accessToken,
144145
'${{ inputs.owner }}',
145146
'${{ inputs.repo }}',
146147
release.id, {
147148
draft: false,
148-
prerelease: '${{ inputs.tag-name }}'.indexOf('-rc') > 0
149+
prerelease: isPrerelease,
150+
make_latest : !isPrerelease
149151
}
150152
)
151153
- name: update check-run

0 commit comments

Comments
 (0)