Future: new gems and improvements towards v0.1.0 and v1.0.0.

[drnic]

Soon I will look to cut a new rubygem release, merge some PRs, and cut an additional rubygem release. But before I do this I want to acknowledge that presently no one is using the rubygem releases and that master branch has been "stable" and used in production for half a decade.

Until the next gem release is cut soon, the only successful way to have used this omniauth plugin has been as a git repository.

gem 'omniauth-uaa-oauth2', git: 'https://github.com/cloudfoundry/omniauth-uaa-oauth2'

This means that all users of omniauth-uaa-oauth2 are currently deploying to production whatever is on master/HEAD (after they next run bundle update).

I want to acknowledge that I'm aware of this and will try hard to not merge any PRs into master that might possibly be backwards incompatible.

The first version I'll cut will be v0.1.0 based on whatever is on master right now (plus some licensing updates).

Then I will merge in the https://github.com/cloudfoundry/omniauth-uaa-oauth2/pulls which will:

• move the project to ruby2 testing and its {key: value} hash syntax ruby2 - testing last 3 ruby in travis; use {key: value} syntax #16
• add support for custom root CAs options support ssl_ca_file and ssl_store_cert for custom root CAs #14
• remove the deprecation warning when decoding access tokens to get the expiry date avoid deprecation warnings; explicit ignore verify #12

Then I will cut v1.0.0; and close this ticket.

If you have any concerns or requests, reply below. ❤️ @drnic

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/159157330

The labels on this github issue will be updated when the story is started.

[drnic]

v1.0.0 released