-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
build(cli): build nix binaries for both x64 and arm64 #2492
Conversation
I fixed the PR's subject to conform to Conventional Changelog's formatting, but can't re-run the lint job to verify. I'm afraid one of y'all may need to re-run it to verify it passes now. |
Build x86 and arm64 binaries for the linux, macos, and alpine platforms. Adjust the installation script to detect the OS and architecture then download the correct binary.
Add quotes to shell variables to prevent unexpected behavior if the install script is executed from a directory with a space in its name.
Thanks! |
Hi. I face an issue in downloading the image in This is the link to the doc: https://meta.stoplight.io/docs/spectral/b8391e051b7d8-installation#executable-binaries Is there a plan to fix this issue? Is it possible to upload the binaries with arch-suffix? Thanks! |
@alireza-mht done! |
@P0lip Thanks! |
🎉 This PR is included in version 6.9.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
Fixes #2189.
Checklist
Not applicable. Tests were run, and documentation was checked, but these changes don't require test or documentation changes.
Does this PR introduce a breaking change?
Release binaries for Linux, macOS, and Alpine now have their arch suffixed to their names. Prior to the change, release binaries were named:
spectral-linux
spectral-macos
spectral-alpine
They are now:
spectral-linux-x64
spectral-linux-arm64
spectral-macos-x64
spectral-macos-arm64
spectral-alpine-x64
spectral-alpine-arm64
The installation script has been updated to work with this change, but it breaks workflows for users or systems who depend on the original naming pattern.
I can copy the x64 binaries to files with their original name to prevent the BC break, but that could make the file list in the release look a little confusing.
Additional context
Unrelated to binary builds is a fix to the installation script that will prevent bugs when executing the script from a directory with a space in its name.
Thanks for checking this out! I'm open to commentary and suggestions.