-
Notifications
You must be signed in to change notification settings - Fork 0
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
Download release binary #2
Conversation
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.
cool! one little comment
src/index.ts
Outdated
const artifact = artifacts.find( | ||
(a) => a.goos === goOs && a.goarch === goArch | ||
const asset = validRelease.assets.find( | ||
(a) => a.name.includes(nodeArch) && a.name.includes(nodeType) |
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.
you should be able to just construct the expected binary name and check for an exact match right? that seems a little more straightforward and less likely to lead to something weird happening
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.
Good call
e6bd2ad
to
640f4a4
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.
LGTM!
This change updates the action code to download the correct release binary from our dedicated release repo at https://github.com/Enterprise-CMCS/mac-fc-report-event-releases. It adds a
version
input that uses semver to parse the input, and atoken
input that uses theGITHUB_TOKEN
as its default. This lets us get around the low rate limit imposed by the GitHub API on unauthenticated requests.Testing:
test-action
workflow