Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH release action: Fix "packages" name conflict #684

Merged
merged 2 commits into from
Feb 20, 2025
Merged

Conversation

lfittl
Copy link
Member

@lfittl lfittl commented Feb 20, 2025

During the release process we group together the created packages as an artifact, to then upload them individually to the GitHub release entry.

Previously this was able to use a single "packages" zip file for both x86_64 and arm64 packages, but we now need to split this since we split the actions.

During the release process we group together the created packages as
an artifact, to then upload them individually to the GitHub release entry.

Previously this was able to use a single "packages" zip file for both
x86_64 and arm64 packages, but we now need to split this since we split
the actions.
@lfittl lfittl requested a review from a team February 20, 2025 21:46
We've previously used Ubuntu 20.04 for the x86_64 binary, to avoid
building a too new glibc. Unfortunately with Ubuntu 20.04 GH actions
on the way out, this seems to no longer work reliably. Separately, we
were already building the arm64 packages with an undefined Ubuntu version
(likely 24.04?).

To fix, consistently use Ubuntu 22.04 (glibc 2.35) for both x86_64 and
arm64. This also switches to GitHub's ARM runners from Ubicloud, since
Ubicloud does not offer tagged Ubuntu versions in their runners.
@@ -56,7 +54,7 @@ jobs:
- name: Set up Go 1.x
uses: actions/setup-go@v5
with:
go-version: 1.21
go-version: 1.23
Copy link
Member Author

Choose a reason for hiding this comment

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

Looks like this was missed in the Go version change by accident.

Copy link
Contributor

Choose a reason for hiding this comment

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

ah good catch, thanks for fixing this!

@lfittl lfittl merged commit d2a7499 into main Feb 20, 2025
3 checks passed
@lfittl lfittl deleted the fix-release-action branch February 20, 2025 22:19
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