pod_push
Push a Podspec to Trunk or a private repository
| pod_push | |
|---|---|
| Supported platforms | ios, mac |
| Author | @squarefrog |
4 Examples
# If no path is supplied then Trunk will attempt to find the first Podspec in the current directory.
pod_push
# Alternatively, supply the Podspec file path
pod_push(path: "TSMessages.podspec")
# You may also push to a private repo instead of Trunk
pod_push(path: "TSMessages.podspec", repo: "MyRepo")
# If the podspec has a dependency on another private pod, then you will have to supply the sources you want the podspec to lint with for pod_push to succeed. Read more here - https://github.com/CocoaPods/CocoaPods/issues/2543.
pod_push(path: "TMessages.podspec", repo: "MyRepo", sources: ["https://github.com/username/Specs", "https://github.com/CocoaPods/Specs"])
Parameters
| Key | Description | Default |
|---|---|---|
use_bundle_exec |
Use bundle exec when there is a Gemfile presented | false |
path |
The Podspec you want to push | |
repo |
The repo you want to push. Pushes to Trunk by default | |
allow_warnings |
Allow warnings during pod push | |
use_libraries |
Allow lint to use static libraries to install the spec | |
sources |
The sources of repos you want the pod spec to lint with, separated by commas | |
swift_version |
The SWIFT_VERSION that should be used to lint the spec. This takes precedence over a .swift-version file | |
skip_import_validation |
Lint skips validating that the pod can be imported | |
skip_tests |
Lint skips building and running tests during validation | |
use_json |
Convert the podspec to JSON before pushing it to the repo | |
verbose |
Show more debugging information | false |
use_modular_headers |
Use modular headers option during validation | |
synchronous |
If validation depends on other recently pushed pods, synchronize | |
no_overwrite |
Disallow pushing that would overwrite an existing spec | |
local_only |
Does not perform the step of pushing REPO to its remote |
* = default value is dependent on the user's system
Documentation
To show the documentation in your terminal, run
fastlane action pod_push
CLI
It is recommended to add the above action into your Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal
fastlane run pod_push
To pass parameters, make use of the : symbol, for example
fastlane run pod_push parameter1:"value1" parameter2:"value2"
It's important to note that the CLI supports primitive types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g. param:"1,2,3"). Hashes are not currently supported.
It is recommended to add all fastlane actions you use to your Fastfile.
Source code
This action, just like the rest of fastlane, is fully open source, view the source code on GitHub