Skip to content

Fix macos-verify.sh for relative paths - #260

Merged
danielehrhardt merged 1 commit into
mainfrom
fix/macos-verify-relative
Oct 28, 2026
Merged

danielehrhardt merged 1 commit into
mainfrom
fix/macos-verify-relative

Conversation

@danielehrhardt

Copy link
Copy Markdown
Contributor

The v0.2.31 release run signed and notarized the macOS binaries and apps fine, but scripts/macos-verify.sh then exited silently: it extracted the signing certificate after a cd into a temp folder, so the relative paths the workflow passes were not found (my local tests used absolute paths).

Now the certificate is extracted with --extract-certificates=<prefix> without changing directory, and a missing certificate gives a clear error.

Tested with relative paths (a signed binary, the v0.2.30 DMG and update bundle, and rel dir/Godmode Bot.app with spaces): all pass.

The certificate was extracted after a cd into a temp folder, so relative
paths (as the release workflow passes them) were not found and the check
exited without a message. Extract with a path prefix instead.
@danielehrhardt
danielehrhardt merged commit d5a54ab into main Oct 28, 2026
8 checks 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.

1 participant