Added workflow to do a CocoaPods release#38
Open
ArielDemarco wants to merge 1 commit intomw99:masterfrom
Open
Conversation
|
@mw99 Do you think this PR might help you run the process without having to find the actual machines, I think its a great option. |
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.
Overview
This PR is related to the discussion in this other PR. It introduces a GitHub Actions workflow that enables pushing the
DataCompression.podspecto CocoaPods.Details
The workflow will run in two scenarios:
x.y.z)It uses the
macos-latestrunner (as of now, this corresponds to macOS 14).The workflow exposes a
dryRunmode. When enabled, it will lint the podspec usingpod lib lintinstead of pushing it to trunk viapod trunk push.Note
When triggered by a tag push, the workflow always runs with
dryRun: false, meaning it will push to CocoaPods trunk.Important
To function properly, a secret named
COCOAPODS_TRUNK_TOKENmust be added to the repository’s GitHub Actions secrets.Test
I’ve tested this action locally in my fork:
workflow_dispatchmechanism (aka. manually).COCOAPODS_TRUNK_TOKENin my fork, but it reached the push step, so it’s very likely that everything is set up correctly).