Skip to content

ci: add prerelease#253

Open
yejseo01 wants to merge 4 commits intomainfrom
ci/prerelease-release-workflow
Open

ci: add prerelease#253
yejseo01 wants to merge 4 commits intomainfrom
ci/prerelease-release-workflow

Conversation

@yejseo01
Copy link
Copy Markdown
Contributor

Changes

  • Enable pre-release to make e2e testing of release process less hazardous

@yejseo01 yejseo01 requested a review from a team as a code owner April 30, 2026 15:14
Comment on lines +42 to +47
current="$(svu current)"
if [[ "$current" == *-rc.* ]]; then
next="$(svu prerelease --prerelease rc)"
else
next="$(svu next --prerelease rc.1)"
fi
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this actually necessary or can we just do this?

Suggested change
current="$(svu current)"
if [[ "$current" == *-rc.* ]]; then
next="$(svu prerelease --prerelease rc)"
else
next="$(svu next --prerelease rc.1)"
fi
next="$(svu next --prerelease rc)"

Copy link
Copy Markdown
Contributor

@awphi awphi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As @Luke-Parkin pointed out, we need to be mindful of topo upgrade and the release scripts which have a dependency on the https://artifacts.tools.arm.com/devx-topo/ index to work out what the latest version is.

Currently tags on the end of version numbers are stripped so while this change wouldn't result in someone downloading an unsigned binary by accident it would break these upgrade mechanisms while a -rc release is the latest.

I guess we need to adjust the upgrade mechanisms to account for this but we need to wait for users to upgrade to topo version that has these changes. Alternatively (my preference) - upload these "release candidates" into a separate folder/repo on artifactory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants