Update dependency doorkeeper-openid_connect to v1.10.2#11756
Merged
renovate[bot] merged 1 commit intoJun 23, 2026
Conversation
4b81af9 to
5162f08
Compare
Contributor
Code Coverage Report: Only Changed Files listed
Minimum allowed coverage is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.10.1→1.10.2Release Notes
doorkeeper-gem/doorkeeper-openid_connect (doorkeeper-openid_connect)
v1.10.2Compare Source
>= 3.2.i18n 1.15.0uses theFiber[]storage API which only exists on Ruby 3.2+, so the Ruby 3.1 CI row no longer loads; the matrix now tests Ruby 3.2 as the minimumfail-fast: falsein CI matrix so a single failing job no longer cancels the restselect_account_for_resource_ownercan now receivenilas the first argument.auth_time_from_access_tokenconfig option in the README (per-grantauth_time), clarifying that it only affects the ID Tokenauth_timeclaim and notmax_ageenforcementbundle exec rake serverfor the test applicationErrors::MissingRequiredClaiminstead of silently dropping a blank REQUIRED ID Token claim (iss/sub/aud/exp/iat) inIdToken#as_json, which previously could emit a non-conformant ID Token (OIDC Core 1.0 §2). OPTIONAL claims such asnonce/auth_timeare still omitted when blankclient_secret_expires_atmember (value0, never expires) in the Dynamic Client Registration response whenever aclient_secretis issued (RFC 7591 §3.2.1 / OpenID Connect Dynamic Client Registration 1.0 §3.2)spec/dummy) for exercising the OpenID Connect endpoints by hand — replacing the rails console + curl workflow with forms for Setup, Discovery, Authorization (code / implicit / PKCE / nonce / prompt /max_age), token exchange, UserInfo, introspection and revocationConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.