Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade CocoaPods to v1.0.0.beta.5 #19804

Closed
wants to merge 2 commits into from

Conversation

orta
Copy link
Contributor

@orta orta commented Mar 14, 2016

No description provided.

@orta
Copy link
Contributor Author

orta commented Mar 14, 2016

uh oh, let's find that sha

@vitorgalvao
Copy link
Member

Updating the :checkpoint value in appcast is required. You can find it with curl --silent --compressed "{{appcast_url}}" | sed 's|<pubDate>[^<]*</pubDate>||g' | shasum --algorithm 256 | awk '{ print $1 }'.

Alternatively, you may wish to use cask-repair. It can at once update the cask鈥檚 version (according to what you give it) taking care of updating both the cask鈥檚 sha256 and the appcast鈥檚 :checkpoint, while still giving you the chance to perform other manual fixes.

You can easily install it with brew install vitorgalvao/tiny-scripts/cask-repair. cask-repair --help will show you some options, but as a whole the script will guide you through the update process.

Also, please squash your commits.

@orta
Copy link
Contributor Author

orta commented Mar 14, 2016

OK, cool, thanks.

I'm gonna update our tooling and open another PR once that's done 馃憤 (don't want to leave hanging PRs around for you. Can't be too sure when I'll get around to this. )

@orta orta closed this Mar 14, 2016
@vitorgalvao
Copy link
Member

Sure thing. I鈥檒l update this one for you, then. Already done in #19808.

The command I ran was simply cask-repair --cask-version 1.0.0.beta.5 --blind-submit cocoapods, and it was done. It even takes care of submitting the PR automatically.

@orta
Copy link
Contributor Author

orta commented Mar 14, 2016

Thanks @vitorgalvao ! 馃憤 appreciated - all of this PR is done via a script as a part of our deploy process - so I want to make sure others don't need to have cask-repair installed in order to ship builds in the future

@adidalal adidalal removed the awaiting user reply Issue needs response from a user. label Apr 12, 2016
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants