mirror of
https://github.com/OAuthSwift/OAuthSwift.git
synced 2026-04-26 12:45:52 +03:00
[GH-ISSUE #649] 👥 Add contributor: phatblat #426
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#426
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 @phatblat on GitHub (Apr 27, 2021).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/649
Greetings! My team has started using this fabulous library in our inner-source auth library which will be used in 6 (and probably more) of our company's public iOS apps. We are using PingFederate as our OAuth server.
I have noticed that there are two new GitHub releases (2.1.1 & 2.1.2) that have been tagged but not yet released to CocoaPods trunk. Version 2.1.0 is the latest that shows up on CocoaPods.
I would like to help out with publishing these and future releases to CocoaPods. I just need @phimage or @dongri to run the following command to add me as an owner of this pod.
Note that all CocoaPods trunk session keys have been wiped due to a recent trunk vulnerability, so you'll probably need to authenticate again with
pod trunk register.I have lots of experience publishing libraries to CocoaPods trunk and also publish our own 20+ internal iOS libraries to a private repo.
I can also help out with issue triage and PR review if you would be open to adding me as a contributor on this repo.
@phimage commented on GitHub (Apr 28, 2021):
Hi,
I have made cocoapod push (without any test, I do not like that 😭)
(change target tvos to 13 to make it pass)
I do not use anymore cocoapod so sorry for the late...
Only @dongri could add you on github or cocoapod
I agree with that
@dongri commented on GitHub (Apr 28, 2021):
@phimage Thank you for your support!
@phatblat Hi, Ben
I have added you to cocoapod.
I've also added it to this repository
@mesopelagique commented on GitHub (Apr 28, 2021):
(posted with bad account: I am phimage)
for the 2.1.3 or 2.2.0
I have lost all my data, and so my test file with all my oauth service provider tokens , so without testing I am not confident
I try to figure the change log and see If no regression
https://github.com/OAuthSwift/OAuthSwift/compare/2.1.2...master
Checked
(
#602 fix warning
)
to check
@phatblat commented on GitHub (Apr 29, 2021):
Thanks! I look forward to working with you both and the users of this fabulous library!
I'm going to create a couple of issues to track the release of 2.1.1 and 2.1.2 to CocoaPods mostly as a place to note any hiccups or things I learn in the process. Meanwhile, I'll start reviewing the recent history to figure out whether the next release should be a patch or minor release.
I did notice that the public API was changed in 2.1.1 when
ASWebAuthenticationURLHandlerhad theprefersEphemeralWebBrowserSessionparameter added to the constructor. Technically, this is actually a breaking change since there is no default for the value, but would be a minor version if a default value were added so that the parameter didn't need to be added everywhere thatASWebAuthenticationURLHandleris constructed.@phatblat commented on GitHub (Apr 29, 2021):
Nevermind. Looks like 2.1.1 and 2.1.2 are live now on CocoaPods.
@phimage commented on GitHub (Apr 29, 2021):
I didn't care enough if semantic version rules has been broken
@phatblat commented on GitHub (Apr 30, 2021):
I was wrong. There was a default value added in a subsequent commit. So, this was not a breaking API change in 2.1.1.
@phatblat commented on GitHub (Apr 30, 2021):
It doesn't look like I have any permissions on this repo yet. I can't add labels or merge PRs. I wanted to merge #285 before releasing #620 since that's a good change, but I don't have permission.
@mesopelagique commented on GitHub (Apr 30, 2021):
phimage: unfortunately I cannot do anything 😝 ( @dongri ? maybe the role)
, except that I could merge or the moment
#625 I suppose
before releasing something I want to check the #623 that I merge without really checking the code and result
@phatblat commented on GitHub (May 5, 2021):
I'm a collaborator now that I found the invite that @dongri send me 😳
@phatblat commented on GitHub (May 18, 2021):
Regarding #623, RFC-5849 section 3.4.4: PLAINTEXT
The spec lines up with the implementation:
However, the values used are not the
urlEncodedvalues and thus could cause issues if one of those values contained unsupported characters.@phimage commented on GitHub (May 18, 2021):
thanks
So it's better than nothing
we could release or make fix with using maybe one of functions in
github.com/OAuthSwift/OAuthSwift@2384f60031/Sources/String+OAuthSwift.swift@phatblat commented on GitHub (May 18, 2021):
Proposed a fix in #657
@phimage commented on GitHub (May 18, 2021):
merged thanks