Summary:
This PR adds a script to publish pods. It handles different edge cases like:
- The version was already pushed but still you are trying to push it, it will skip in that case and give a proper message.
- This also makes sure that the same version Flipper pod exists before pushing FlipperKit.
- It also has the retry mechanism in place if at all the pod trunk push fails to push.
## Changelog
Updated the workflow to push pods
Pull Request resolved: https://github.com/facebook/flipper/pull/2511
Test Plan:
While pushing already published release:
https://github.com/facebook/flipper/actions/runs/974346766
While pushing new release:
https://github.com/facebook/flipper/actions/runs/978707041
Reviewed By: passy
Differential Revision: D29415078
Pulled By: priteshrnandgaonkar
fbshipit-source-id: f0fb68a2e399802e5719d7be4216d4a5ed6ef782
Summary:
Sample and SampleSwift directly link to the debug version and don't reference `flipperkit_version` which is why the script is failing.
Pull Request resolved: https://github.com/facebook/flipper/pull/2117
Test Plan: hopeitwork
Reviewed By: priteshrnandgaonkar
Differential Revision: D27395244
Pulled By: passy
fbshipit-source-id: 3485731b0489376fbdf987c082ef7d288f66bbe8
Summary: This is suggested as a fix for the consistency issue (https://github.com/facebook/flipper/issues/1638) when interdependent packages published together and one of them cannot find another because it takes time to synchronise published packages to CDN. This fix is suggested here: https://github.com/CocoaPods/CocoaPods/issues/9497.
Reviewed By: mweststrate
Differential Revision: D25184732
fbshipit-source-id: d8d58b33f65ff7e87f935fb7cb85964dbf95dd13
Summary: Had the `PERSONAL_TOKEN` put in place by the OSS oncall. Still won't know if it has the right permissions until we run this. :/
Reviewed By: nikoant
Differential Revision: D24833829
fbshipit-source-id: 4fbf6e0b0abbc50d0b9a1e9b7ca8b02f6e1f5171
Summary:
This diff updates the Github workflow to update pod versions after the release is published on Cocoapods.
## Changelog
- Update Github workflow to update the pod versions till the release is published in Cocoapods.
Pull Request resolved: https://github.com/facebook/flipper/pull/1338
Test Plan:
A PR got created with the updated pod versions after the release was pushed.
https://github.com/facebook/flipper/pull/1365
Reviewed By: passy
Differential Revision: D22456857
Pulled By: priteshrnandgaonkar
fbshipit-source-id: 335996bc1ebb6da309d3f60a8f3401559e0a83c7
Summary:
This PR adds GH action to create PR with the updated Podfile.lock when a new tag is released.
## Changelog
- Add GH action to automatically create PR with updated Podfile.lock.
Pull Request resolved: https://github.com/facebook/flipper/pull/1097
Test Plan: I was not able to test it on a release of tag. But I tested it by triggering the workflow on a push to the branch. It created a PR like [this](https://github.com/facebook/flipper/pull/1110).
Reviewed By: jknoxville
Differential Revision: D21381996
Pulled By: priteshrnandgaonkar
fbshipit-source-id: 2dffa0f71f7e211541728acb06aea5763ae53f47
Summary:
This PR adds a github action to publish pods on a new tag. It also tries to fix a race condition which happens when we try to publish FlipperKit pod. During the release of FlipperKit pod, we rely on the newly published Flipper Pod, and sometimes the release of Flipper Pod takes a time to get updated in the cocoapods trunk.
This is a known issue by the Cocoapods and they will be shipping a fix to this in Cocoapods 1.10. Till then we can keep retrying for 5 times.
Ref: https://github.com/CocoaPods/CocoaPods/issues/9502#issuecomment-579486258
## Changelog
- Adds Github actions to publish cocoapods.
- Removes the Circle CI config to publish on cocoapods
Pull Request resolved: https://github.com/facebook/flipper/pull/1083
Test Plan: I tested this action by running it on this PR and it worked fine.
Reviewed By: jknoxville
Differential Revision: D21348084
Pulled By: priteshrnandgaonkar
fbshipit-source-id: f33f3cdef43ae032ad42c94db72323212e40ec67
