You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's still no ci/cd pipeline for a cocoapods release.
What solution would you like?
Such pipeline has to be implemented as long as we're providing cocoapods support (which is for now until 3.*.* release branch are active).
Requirements
This pipeline should be implemented for both modules: Web3Code.podspec and Web3Swift.podspec.
This pipeline should be triggered only on developer to master merge, as cocoapods support are just an additional feature of our lib, and it's never in first place in development process.
So in case of new code has been broke cocoapods in a some way a release should be provided in SPM anyway, while the cocoapods release would be provided in future by a separate patch by fixup PR into develop.
So as it said above, those checks would not be a merge or release blockers as pod releases happening manually yet, they just to be proposed to made cocoapods release more convenient to a maintainer.
Any additional context?
An appropriate way to check whether pod is building locally (e.g. that the code is ok ready to be published) is: pod lib lint --allow-warnings POD_NAME.podspec
The text was updated successfully, but these errors were encountered:
What context is your feature request related to?
There's still no ci/cd pipeline for a cocoapods release.
What solution would you like?
Such pipeline has to be implemented as long as we're providing cocoapods support (which is for now until 3.*.* release branch are active).
Requirements
Web3Code.podspec
andWeb3Swift.podspec
.developer
tomaster
merge, as cocoapods support are just an additional feature of our lib, and it's never in first place in development process.So in case of new code has been broke cocoapods in a some way a release should be provided in SPM anyway, while the cocoapods release would be provided in future by a separate patch by fixup PR into
develop
.So as it said above, those checks would not be a merge or release blockers as pod releases happening manually yet, they just to be proposed to made cocoapods release more convenient to a maintainer.
Any additional context?
An appropriate way to check whether pod is building locally (e.g. that the code is ok ready to be published) is:
pod lib lint --allow-warnings POD_NAME.podspec
The text was updated successfully, but these errors were encountered: