Repository navigation
CI: GitHub Actions signed/notarized draft release workflow - #106
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Release workflow so signed, notarized MijiaBar builds can be produced on GitHub Actions. This PR does not publish a release, bump
docs/VERSION, or update the live Sparkle appcast.What this does
.github/workflows/release.yml, triggered by Actions → Release → Run workflow (workflow_dispatch) and by PRs that touch this workflow or the packaging/appcast scripts (ad-hoc dry run, no secrets).workflow_dispatchwithdraft-release=true(the default), assets are attached to a draft GitHub release only. The workflow never publishes, never pushes a tag, and never commitsdocs/appcast.xmltomain.scripts/package.shnow supportsASC_API_KEY_*,KEYCHAIN, andREQUIRE_NOTARIZATIONfor CI, while keeping the local Developer ID +MijiaBar-notarypath as a backup on Mac mini A.scripts/generate-appcast.shdefaults enclosure URLs toBeastry/MijiaBar(oldneardws/MijiaBardownload links still redirect). Site/feed URLs onwww.neardws.comare unchanged.docs/release-notes/v0.1.16.mdand documents secret names indocs/UPDATING.md.Secrets (names only)
Signing:
DEVELOPER_ID_P12_BASE64,DEVELOPER_ID_P12_PASSWORD,DEVELOPER_ID_IDENTITY,APPLE_TEAM_ID,KEYCHAIN_PASSWORDNotarization:
ASC_API_KEY_ID,ASC_API_ISSUER_ID,ASC_API_KEY_P8_BASE64Updates:
SPARKLE_ED_PRIVATE_KEY(MijiaBar's own key; must matchSUPublicEDKey)ASC_API_ISSUER_IDis still required before a notarized 0.1.16 run. This PR's CI is the secret-free ad-hoc dry run only. Existing signing material on Mac mini A is kept as a backup.