Skip to content

Conversation

@meganemura
Copy link
Contributor

This is a successor of #325.

@meganemura
Copy link
Contributor Author

@josephpage @pboling Would you please review this?

@coveralls
Copy link

coveralls commented Oct 4, 2018

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

10 similar comments
@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 709

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 706: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@pboling pboling added this to the 3.0.0 milestone Oct 5, 2018
@pboling pboling added the DO NOT MERGE Do. Not. Merge. label Oct 5, 2018
@pboling
Copy link
Member

pboling commented Oct 5, 2018

I need to review this for breaking changes.

We are not dropping any existing support for old Rubies in the 2.0.0 release.

# Base64.strict_encode64 is not available on Ruby 1.8.7

This might need to go into the follow up 3.0.0 release.

@meganemura
Copy link
Contributor Author

@pboling

In https://github.com/oauth-xx/oauth2/milestone/1 and #325,

2.x is the last version series that will have Ruby 1.9/2.0/2.1/2.2 support.

So, I think 2.x release does not need to support ruby 1.8.

@pboling
Copy link
Member

pboling commented Oct 5, 2018

Oh good point! I need to add a Ruby support matrix to the Readme.

@pboling pboling removed the DO NOT MERGE Do. Not. Merge. label Oct 5, 2018
@pboling pboling modified the milestones: 3.0.0, 2.0.0 Oct 5, 2018
@pboling pboling self-assigned this Oct 5, 2018
@pboling pboling self-requested a review October 5, 2018 22:12
Copy link
Member

@pboling pboling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@pboling pboling merged commit 5436fa3 into ruby-oauth:master Oct 5, 2018
@meganemura meganemura deleted the strict_encode64 branch October 6, 2018 00:49
@pboling pboling added the in Changelog Has been added to Changelog label Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in Changelog Has been added to Changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants