-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Lib comaptibility w/ v1 and v2? #26
Milestone
Comments
This is expected. See #15 |
If that's the case (and it is, see also) then the README is misleading. It claims to be compatible, yet the instruction in the readme, Ideally v1 could ship with a dummy NO-OP file there so we can use the same code in libraries targetting compatibility with both versions. |
pboling
added a commit
to pboling/omniauth-jwt2
that referenced
this issue
Dec 1, 2023
ioquatix
pushed a commit
that referenced
this issue
Dec 1, 2023
Released in v1.0.2. |
pboling
added a commit
to pboling/omniauth-jwt2
that referenced
this issue
Dec 6, 2023
…v2 (#6) * 🐛 Fix compatibility with omniauth v1 & v2, rack v2 & v3, rack-session v1 & v2 - Ref: rack/rack-session#26 * 👷 Add ancient build for Ruby 2.2 & 2.3 * 💚 Better handling of ancient ruby scenario * 💚 Ancient ruby support * ✨ Support Ruby 2.2 & 2.3
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
When I use a "legacy" gemfile in this project I see the following when updating the bundle:
That is as expected.
I have this at the top of my
spec_helper.rb
, which is documented as the correct usage in theREADME.md
of both thestable-v1
branch and themain
branch:But when I run tests I get an error:
The text was updated successfully, but these errors were encountered: