Skip to content

Conversation

@pcai
Copy link

@pcai pcai commented Jun 1, 2016

Thank you for providing this gem. I suspect that many projects, ours included, use oauth2 >= 1.0 which is not compatible with this gemspec. Is there a reason this can't be updated? We're using a forked version with this change successfully at privy.com, although there don't seem to be any tests I can run to confirm the change.

@coveralls
Copy link

coveralls commented Jun 1, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 59b7ca0 on Privy:master into e038950 on mailup:master.

@coveralls
Copy link

coveralls commented Dec 18, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling c579b35 on Privy:master into e038950 on mailup:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c579b35 on Privy:master into e038950 on mailup:master.

@pcai
Copy link
Author

pcai commented Jan 6, 2021

closing for now. let us know if there's any interest in picking this back up.

@pcai pcai closed this Jan 6, 2021
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

Successfully merging this pull request may close these issues.

3 participants