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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release version 2.1.2 to CocoaPods #615

Closed
3 of 10 tasks
moberwasserlechner opened this issue Jul 26, 2020 · 6 comments
Closed
3 of 10 tasks

Release version 2.1.2 to CocoaPods #615

moberwasserlechner opened this issue Jul 26, 2020 · 6 comments

Comments

@moberwasserlechner
Copy link

moberwasserlechner commented Jul 26, 2020

Description:

Would it be possible to release the latest bugfix release to CocoaPods.org?

Currently only version 2.1.0 can be obtained from there. (see https://cocoapods.org/pods/OAuthSwift)

Thx & BR, Michael

OAuth Provider? (Twitter, Github, ..):

OAuth Version:

  • Version 1
  • Version 2

OS (Please fill the version) :

  • iOS :
  • OSX :
  • TVOS :
  • WatchOS :

Installation method:

  • Carthage
  • CocoaPods
  • Swift Package Manager
  • Manually
@phimage
Copy link
Member

phimage commented Jul 27, 2020

I will do when I have some time, If I can I prefer to make some test before releasing.
You could use HEAD code in podfile

@ghowen
Copy link

ghowen commented Jul 27, 2020

@phimage Nice one! I always seem to forget this. Just on a side note: :head is deprecated and has been replaced with :git. So to get the master branch one would add

pod 'OAuthSwift', :git => 'https://github.com/OAuthSwift/OAuthSwift.git'

to one's podfile.

Anyways, thanks for the library. OAuth1ing to OpenStreetMap is a breeze with this 👍

@moberwasserlechner
Copy link
Author

@ghowen @phimage Thank you both I didn't know that this was possible with cocoapods.

@vgritsenko
Copy link
Contributor

While it is possible to use :git => ... branch => with CocoaPods in the Podfile, the same is not possible for other pods which declare OAuthSwift as a dependency. As a result, any such pod would fail validation and it would not be possible to release such pod automatically:

pod repo push <repo> MyAwesomePod.podspec --<parameters>

In our case we are waiting for the 2.1.3 release which brings in addition for token refresh. Would it be possible to release 2.1.3 sooner?

#620

@macbellingrath
Copy link

@phimage any update on the release?

@phatblat
Copy link
Collaborator

phatblat commented Apr 30, 2021

@macbellingrath 2.1.2 was published to CoaoPods a couple days ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants