Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump the oauth2 gem #76

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

bump the oauth2 gem #76

wants to merge 1 commit into from

Conversation

almathew
Copy link
Contributor

No description provided.

@@ -21,9 +21,10 @@ Gem::Specification.new do |spec|
spec.require_paths = ['lib']

spec.add_dependency 'aptible-resource', '~> 1.0'
spec.add_dependency 'concurrent-ruby', '1.3.4'
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@@ -15,7 +15,7 @@ jobs:
strategy:
fail-fast: false
matrix:
RUBY_VERSION: [2.2, 2.3, 2.5, 2.6]
RUBY_VERSION: [2.6, 2.7]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I wanted to add 3.x since that's what our APIs are on, but that breaks rubocop, and I don't really want to deal with that when all I'm trying to do is make what should be a minor version bump

@almathew almathew requested a review from mdelaossa January 21, 2025 14:43
@almathew almathew marked this pull request as ready for review January 21, 2025 14:43
@almathew
Copy link
Contributor Author

@mdelaossa I'm assigning you as reviewer because you skipped doing this previously, and the why has mostly been lost to the ether as far as I can tell.

I want this for deploy-api, where it appears tests are all passing.
I also tested against sweetness since that has the biggest variation from everything else.

Stupidly, I'm doing this because I want to upgrade faraday in deploy-api, and there's like 5 more blockers between me and doing that, so if there's a reason I shouldn't be doing this, it would be very easy to convince me not to.

Copy link

@mdelaossa mdelaossa left a comment

Choose a reason for hiding this comment

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

I think the main reason for not updating was that things were becoming complicated back then and touching yet another repo was complicating things even more. I don't think I had an actual problem with oauth2 - I just quickly realized I didn't have to, so didn't do it

This looks good though!

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.

2 participants