-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add musl binaries to the Standalone CLI #15567
Conversation
4d64ba4
to
c6cb9a9
Compare
We have separate MUSL binaries so there’s no longer a reason for us to bundle GLIBC and MUSL node addons
It fixes building Musl standalone binaries
b4f4e38
to
4b03b20
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Schweet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually need to add this here as well: https://github.com/tailwindlabs/tailwindcss/blob/next/.github/workflows/release.yml#L265-L271. If you comment out the npm release part it should be fine to run the release pipeline in this PR too and we can test the artifacts that are uploaded to the run.
Are we sure that it's fine? I've had the release workflow overwrite / replace an existing release before unintentionally. edit: I made a copy of the release notes / binaries in case something goes awry. |
e162c51
to
4e19bbe
Compare
Closes #15031
This adds musl binaries for the Standalone CLI on Linux aarch64 (ARM 64-bit) and x86_64 (Intel/AMD 64-bit).
I tested this by temporarily running the release workflow (without publishing) to build the Standalone CLI, downloading the artifacts, and running the musl binaries in two docker containers.
(sorry for the potato screenshot — tested x64 through my AMD Windows machine over parsec)