Repository navigation
ci(release): a failed release opens an issue; the next good one closes it - #918
Merged
Merged
Conversation
…s it v0.8.245 through v0.8.249 all failed at notarization (revoked Apple app-specific password) and nothing said so for a day. The report job opens one 'Release builds are failing' issue on failure, comments on later failures, and closes it when a release builds.
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.
A release that fails now tells you: a GitHub issue opens, and it closes itself when the next release builds.
Why: v0.8.245 through v0.8.249 all failed at notarization (
HTTP status code: 401. Invalid credentials; theAPPLE_PASSWORDapp-specific password had been revoked). Nothing flagged it. Merges kept landing and versions kept being tagged, but no Juno build was published for about a day. Found 2026-10-30 while building the Demo. The password was replaced the same day.How: a
reportjob afterbuild-tauri(skipped when the gate skips the tag-triggered duplicate, or the run is cancelled):Only
issues: writeon that job.DRI: Claude (this session).