Allow setting the make latest flag when creating a release. #3199
Labels
ci
Continuous integration / automation
low priority
Nice to have for this milestone, can be pushed out if needed
proposal
Proposed change to how something works (usually larger or more fundamental than a feature request)
Comments
trackleft
added
ci
|
the action we use just release v2, which does what we need . |
trackleft
changed the title
danahertzberg
modified the milestones:
2.9.x Patch Release Issues,
2.10.x Patch Release Issues
trackleft
added a commit
that referenced
this issue
Oct 26, 2024
32 tasks
32 tasks
bberndt-uaz
pushed a commit
that referenced
this issue
Nov 1, 2024
bberndt-uaz
pushed a commit
that referenced
this issue
Nov 1, 2024
joeparsons
pushed a commit
that referenced
this issue
Nov 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Quickstart supports two release branches (minimum) at any given time.We need to create releases for both the latest release branch and the previous release branch.One release (from the latest release branch) should be marked latest.One release (from the previous release branch) should not be marked latest.At the moment, the action we use does not allow for this. https://github.com/az-digital/az_quickstart/blob/main/.github/workflows/create-release.yml#L52The github action "create release" which is an archived repo, recommends the following actions for this.https://github.com/actions/create-release
elgohr/Github-Release-Actionmarvinpinto/action-automatic-releasessoftprops/action-gh-release <-- the one we currently use that doesn't allow marking a release as latest.ncipollo/release-action <-- This one allows marking a release as latest.I think we should also take the latest flag into account with this ticket: az-digital/az-quickstart-pantheon#51
See softprops/action-gh-release#304
The text was updated successfully, but these errors were encountered: