Introduce working CI/CD through GitHub Actions#1034
Open
iBotPeaches wants to merge 6 commits intoCocoaPods:masterfrom
Open
Introduce working CI/CD through GitHub Actions#1034iBotPeaches wants to merge 6 commits intoCocoaPods:masterfrom
iBotPeaches wants to merge 6 commits intoCocoaPods:masterfrom
Conversation
segiddins
approved these changes
Mar 14, 2026
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.
Problem
CI/CD has decayed for 2 reasons. The images are no longer supported (ubuntu-20) and the actions used (checkout-v1) are no longer supported. This means they instant fail.
Solution
setup-rubyis far more powerful with caching built in and more. We leverage that in order to reduce the code needed for manual gem cache creation. This turns CI pipelines into about 6 lines of code.Meta
Until my PR is approved for CI to run - you'll have no proof it works. So here is my fork and a test PR for proof. You can see failures for Ruby 3.4 & 4.0 here which I can do a follow-up PR for post merge.