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.

Sign up for GitHub

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

Jump to bottom

Sign / notarize the Mac binaries #1712

Open
wyardley opened this issue Mar 23, 2023 · 4 comments
Open

Sign / notarize the Mac binaries #1712

wyardley opened this issue Mar 23, 2023 · 4 comments
Assignees
@hessjcg
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@wyardley
Copy link

wyardley commented Mar 23, 2023 •
edited by enocom
Loading

Feature Description

In issues like #95, it's suggested to use the direct download vs. using homebrew or even gcloud components .... This proposes signing the Apple binaries in such a way that they can be run locally.

I don't think #1267 will directly handle this, right?
@wyardley wyardley added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Mar 23, 2023
@wyardley wyardley mentioned this issue Mar 23, 2023
Open
@enocom enocom added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Mar 23, 2023
@enocom
Copy link
Member

enocom commented Mar 23, 2023

Helpful: https://artyom.dev/notarizing-go-binaries-for-macos.md

@enocom
Copy link
Member

enocom commented Mar 23, 2023

And this: https://federicoterzi.com/blog/automatic-code-signing-and-notarization-for-macos-apps-using-github-actions/.

We'd need an Apple Developer account, but could otherwise integrate this into our existing build process.

@enocom enocom mentioned this issue Jun 9, 2023
Closed
@enocom enocom mentioned this issue Sep 26, 2023
Closed
@enocom enocom assigned jackwotherspoon and unassigned enocom May 1, 2024
@wyardley
Copy link
Author

Hi @jackwotherspoon - any new news on this one?

@jackwotherspoon
Copy link
Collaborator

Hi @jackwotherspoon - any new news on this one?

Hi @wyardley thanks for the interest here! 😄

We recently did our planning for the upcoming 6 months and signing our binaries was included in the timeline and is high on our list, so hopefully by the end of the year 🤞

@hessjcg will be the one working on it so assigning it over to him

@jackwotherspoon jackwotherspoon added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hessjcg hessjcg

Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@enocom @wyardley @jackwotherspoon @hessjcg