Update dependency doorkeeper-openid_connect to v1.8.9 #9826
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.6.2
->1.8.9
Release Notes
doorkeeper-gem/doorkeeper-openid_connect (doorkeeper-openid_connect)
v1.8.9
v1.8.8
Compare Source
v1.8.7
Compare Source
JWT::JWK::Thumbprint
constant with :: (thanks to @stanhu)v1.8.6
Compare Source
v1.8.5
Compare Source
v1.8.4
Compare Source
Note that v1.8.4 changed the default kid fingerprint generation from RFC 7638 to a format
based on the SHA256 digest of the key element. To restore the previous behavior, upgrade to v1.8.6.
json-jwt
withruby-jwt
to align with doorkeeper-jwt (thanks to @kristof-mattei).v1.8.3
Compare Source
v1.8.2
Compare Source
Doorkeeper::AppliactionMetalController
(thanks @sato11).AuthorizationsController
params (thanks to @nbulaj).v1.8.1
Compare Source
v1.8.0
Compare Source
No changes from v1.8.0-rc1.
v1.7.5
Compare Source
Changes
Bugfixes
v1.7.4
Compare Source
v1.7.3
Compare Source
select_account_for_resource_owner
to support theprompt=select_account
paramv1.7.2
Compare Source
Changes
v1.7.1
Compare Source
Upgrading
This version adds
on_delete: :cascade
to the migration template for theoauth_openid_requests
table, in order to fix #82.For existing installations, you should add a new migration in your application to drop the existing foreign key and replace it with a new one with
on_delete: :cascade
included. Depending on the database you're using and the size of your application this might bring up some concerns, but in most cases the following should be sufficient:Bugfixes
json-jwt
because of CVE-2019-18848 (thanks to @leleabhinav)oauth_openid_requests
tooauth_access_grants
(thanks to @manojmj92)audience
claim when application is not set on access token (thanks to @ionut998)v1.7.0
Compare Source
Changes
v1.6.3
Compare Source
Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.