Skip to content

Update GitHub actions next dev to match released code - #585

Open
marionbarker wants to merge 5 commits into
next-devfrom
update_github_actions-next-dev
Open

marionbarker wants to merge 5 commits into
next-devfrom
update_github_actions-next-dev

Conversation

@marionbarker

Copy link
Copy Markdown
Contributor

Purpose

Align the GitHub actions to match updates recently added to released code (main and dev branch), v3.14.12.

Method

Apply cherry-pick for the relevant commits in order.

Features

  • add an appropriate message for create certs (also called by build) to find an issue quickly and provide instructions to fix the issue
  • remove a confusing fastlane warning
  • remove the build_loop_auto.yml file and restore the automatic building to the build_loop.yml file
    • this was a failed experiment - GitHub disabled the build_loop_auto file once it was in widespread use

ps2 and others added 5 commits November 12, 2026 06:24
The certs step ignored the fastlane certs exit status so that the renewal
check could nuke and recreate an expired certificate. When the check finds
only other, valid Distribution certificates in the team, no renewal runs,
the job still succeeded, and the build later failed at signing with the
same Match error.

Record the certs result and fail the job in that case, pointing to Match's
error about the certificate stored in Match-Secrets.

Reported in LoopKit/Loop#2661.
Wording from marionbarker's review of #573, tested on
her fork, with "is not valid" softened to "could not use": Match can also
fail on a wrong MATCH_PASSWORD or a profile problem.
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.

2 participants