omniauth/omniauth-github
GitHub strategy for OmniAuth
7 Releases
Latest: 5y ago
Require OmniAuth 2.0.0v2.0.0Latest
As of v2.0.0 of this gem, it will require OmniAuth 2.0.0. This is due to changes that came with OmniAuth that required a breaking change in this gem. Because we changed the strategy's code, you should not need to change any omniauth-github specific code. You should refer to OmniAuth's [v2.0.0 release](https://github.com/omniauth/omniauth/releases/tag/v2.0.0) and/or the v2.0 [upgrade guide](https://github.com/omniauth/omniauth/wiki/Upgrading-to-2.0) when upgrading OmniAuth to v2.0.
v1.4.0
Includes changes in #84, #85, #79, #86
v1.3.0
📦 Updates
- Do not include query params in callback URLs (PR #73)
- > In order to be compatible with GitHub Integration's Oauth flow the callback URL must match the same one provided in the integration's settings page. This includes query parameters.
- > Confirmation from Github's team: https://platform.github.community/t/oauth-flow-with-integration-406-not-acceptable/1775/8
- > Thanks to @volmer for handling this!
v1.2.3
📦 Updates
- Loosen OmniAuth requirements (PR: #71)
v1.2.2
🐛 Fixes
- Email without scope (PR: #69; Issue: #68)
v1.2.1
📦 Dependencies
- Bumps omniauth to ~>1.4.0 (Note: Drops support for Ruby 1.8)
✨ Additions
- Adds Rake to development dependencies
v1.2.0
🔒 Security Updates
- Uses `https` for the RubyGems URL to pass `bundler audit`
📦 Dependencies
- Bumps `omniauth` to `~>1.3.2`
- Bumps `omniauth-oauth2` to `~> 1.4.0`
- Bumps `rspec` to `~> 3.5`
📦 Specs
- Updates specs to `RSpec 3+` syntax
📦 Housekeeping
- Ensure similar code formatting in specs
- Bump gem version to `1.2.0`
- ---
📦 Referenced Issues
- Closed #59
- Closed #52
- Closed #57
