-
Notifications
You must be signed in to change notification settings - Fork 69
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
Sign and notarize macos app and installer #1281
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1281 +/- ##
=======================================
Coverage 25.46% 25.46%
=======================================
Files 25 25
Lines 1547 1547
=======================================
Hits 394 394
Misses 1140 1140
Partials 13 13 ☔ View full report in Codecov by Sentry. |
86ab23e
to
037c93b
Compare
f932876
to
af49969
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.
Did you tried to run the create_pkg.sh
script from your computer without the Dev IDs ?
What happens in that case ?
If packaging fails or if the installer does not work, I think we need to add an handling of building with and without the Dev IDs. Otherwise, we won't be able to build from our computers and will require to push, wait for 15min, to then check if it's working. And it's not a viable way of working IMO
I modifier the script, you can now run |
CI: try to sign macos pkg inherit secrets CI: debug CI: change mac os sign secrets CI: fix call to create_pkg.sh ci: try to sign macos ci try CI: mac os notarize CI: export version CI: fix notarize CI: skip stapler CI: debug CI: sign pkg with codesign sign the .app for macos CI: uncomment create pkg now can be run without signing
56c440f
to
cbbafa3
Compare
cbbafa3
to
d0dca83
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.
Good job !
Only a non blocking comment
QA on amr64 and amd64 OK |
Delivery Quality Checklist
Breaking Changes in API:
Does this PR introduce breaking changes in the API?
Changelog:
Version Update Handling:
Have you ensured that the version update by user is handled correctly?
PR Dependency:
Does this PR depend on another PR?
Documentation: