processing / processing/processing4

verify code signature for mac release action before sending for notarization

Open
#1,504 1 comment 1 reaction 1 assignee View on GitHub

@kjhollen is already working on this.

Since Apr 17, 2026.

enhancement
Dominant language
Java
Stars
494
Forks
183
Avg merge
4h 39m
Merged PRs (30d)
3

Description

Most relevant area for this enhancement?

Build process

Feature to enhance

macOS release building

Enhancement details
Enhancement description

Add a step in the release.yml workflow for macOS that checks the code signature before sending the binary to be notarized, so that we have an opportunity to see more output if the process fails. Currently, mac builds fail when notarytool runs, but the logs don't provide enough information to debug effectively.

Benefits

Easier to release new builds for macOS users.

Challenges

Pretty straightforward, I think—see suggested solution in next section.

Additional context

Likely solution is to add this or something similar to the release-macos job:

- name: Verify code signature
  run: |
    codesign -vvv --deep --strict "app/build/compose/binaries/main/Processing.app"
    file "app/build/compose/binaries/main/Processing.app/Contents/MacOS/Processing"

I'll test this out locally & submit a PR if the error output from adding this step is useful.

(with thanks to @SableRaf & Claude for the suggestion)

Would you like to help implement this enhancement?

Yes, I’d like to help with this

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.