mirror of
https://github.com/OAuthSwift/OAuthSwift.git
synced 2026-04-26 20:55:57 +03:00
[GH-ISSUE #469] Tag OAuthSwift with "1.2.2" and tag OAuthSwiftAlamofire with "0.2.0" #307
Labels
No labels
bug
cocoapod
duplicate
enhancement
feature-request
help wanted
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/OAuthSwift#307
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @neoneye on GitHub (Jun 11, 2018).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/469
Description:
The latest release of OAuthSwift is 1.2.1 was made 4 Feb 2018.
When I do
pod lib lintwith my own cocoapod, then I'm seeing warnings related to OAuthSwift and OAuthSwiftAlamofire.In
my-own-pod.podspecit looks like this:I can't switch to
OAuthSwift1.2.1, because that breaksOAuthSwiftAlamofire.I made another issue on OAuthSwiftAlamofire, where I'm more or less writing the same as in this issue.
OAuth Provider? (Twitter, Github, ..):
3rd party provider
OAuth Version:
OS (Please fill the version) :
Installation method:
Library version:
Xcode version:
9.4 (Swift 4.1)
9.3 (Swift 4.1)
9.0 (Swift 4.0)
9.0 (Swift 3.2)
8.x (Swift 3.x)
8.0 (Swift 2.3)
7.3.1
other: (Please fill in the version you are using.)
objective c
@zapjonny commented on GitHub (Jun 22, 2018):
Yes please, fix these deprecations/warnings 🙏🏻 Me using OAuth 1 (Twitter)
@phimage commented on GitHub (Jun 22, 2018):
you can use any commit hash or head in your Podfile
I cannot do it now (i am sick)
@phimage commented on GitHub (Jun 26, 2018):
🎉 Congrats
🚀 OAuthSwift (1.2.2) successfully published
📅 June 26th, 11:55
🌎 https://cocoapods.org/pods/OAuthSwift
👍 Tell your friends!