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.
Checklist
master
Motivation and Context
The new GitHub Actions setup still had some issues on the
Release
workflow:the
workflow_run
triggers whenever one of the dependencies run, and we want it to run when all completejobs'
if
conditions were incorrect, so they always ranthe jobs should use the current git ref and not the head branch.
carthage build was broken, and probably isn't necessary to release a
.framework.zip
anyway people should simply use their dependency manager of choice.The CI was also lacking Carthage verification.
Description
Fix
Release
workflow issues:Remove .framework.zip asset (and respective Carthage build) from Release workflow (isn't used by anyone, AFAIK).
Fix job
if
conditions.Remove explicit
ref
from git checkout steps.Unify
ci
,pod-lint
andspm
workflows intoci.yml
, making it a single dependency forrelease
while being easier to maintain.Add carthage verification job to
ci.yml
.Add new
./scripts/carthage.sh
to work around Xcode 12 issues when running Carthage.