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.

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

Enable MacOS code signing and notarization in GitHub Actions #1267

Merged
merged 6 commits into from
Feb 24, 2025

Conversation

perfectra1n
Copy link
Collaborator

@perfectra1n perfectra1n commented Feb 24, 2025

? path.join(buildPath, `${APP_NAME}.app`, "Contents", "Resources", baseName)
: path.join(buildPath, "resources", baseName);

// prettier-ignore
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you add that comment back in above destPath please?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe I put it back where you asked, now 👀

@perfectra1n
Copy link
Collaborator Author

perfectra1n commented Feb 24, 2025

That afterComplete hook probably cost me 6 hours of my life, wondering why signing and notarization didn't work after Electron said it did everything 😭

(because it moved files around in the .app after it had already been signed, broke the seal on the signature)

So we'll want to keep that in mind if we ever want to sign Windows, that we'll need to modify that afterComplete hook to also not change Windows' files around in any build artifacts after the signature has already been competed...

@eliandoran eliandoran merged commit 4240af6 into TriliumNext:develop Feb 24, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(Bug report) Damaged macOS binary build
3 participants