dependabot[bot] opened a new pull request, #45159:
URL: https://github.com/apache/superset/pull/45159

   Bumps [pyjwt](https://github.com/jpadilla/pyjwt) from 2.14.0 to 2.15.1.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/jpadilla/pyjwt/releases";>pyjwt's releases</a>.</em></p>
   <blockquote>
   <h2>2.15.1</h2>
   <p>See the <a 
href="https://github.com/jpadilla/pyjwt/blob/2.15.1/CHANGELOG.rst";>2.15.1 
changelog</a> for complete release details.</p>
   <h2>2.15.0</h2>
   <p>See the <a 
href="https://github.com/jpadilla/pyjwt/blob/2.15.0/CHANGELOG.rst";>2.15.0 
changelog</a> for complete release details.</p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst";>pyjwt's 
changelog</a>.</em></p>
   <blockquote>
   <h2><code>v2.15.1 
&lt;https://github.com/jpadilla/pyjwt/compare/2.15.0...2.15.1&gt;</code>__</h2>
   <p>Fixed</p>
   <pre><code>
   - Accept trailing Base64URL ``=`` padding when decoding JWS segments, so
     tokens issued by AWS ALB and similar systems verify instead of raising
     ``DecodeError: Invalid crypto padding``. Non-alphabet junk such as
     ``!!!!`` remains rejected 
(`[#1209](https://github.com/jpadilla/pyjwt/issues/1209) 
&lt;https://github.com/jpadilla/pyjwt/issues/1209&gt;`__).
   <h2><code>v2.15.0 
&amp;lt;https://github.com/jpadilla/pyjwt/compare/2.14.0...2.15.0&amp;gt;</code>__</h2>
   <p>Security
   </code></pre></p>
   <ul>
   <li>Wrap recursion errors from deeply nested JWT payloads in 
<code>DecodeError</code>
   instead of exposing a raw <code>RecursionError</code>.</li>
   </ul>
   <p>Added</p>
   <pre><code>
   - Support Python 3.15 by @kytta in 
`[#1202](https://github.com/jpadilla/pyjwt/issues/1202) 
&lt;https://github.com/jpadilla/pyjwt/pull/1202&gt;`__
   <p>Changed
   </code></pre></p>
   <ul>
   <li><code>JWKSetCache</code> now stores the parsed <code>PyJWKSet</code> 
rather than the raw JWKS
   payload, so a cache hit no longer re-parses every key. 
<code>JWKSetCache.put()</code>
   accepts either form and raises <code>PyJWKSetError</code> for anything else. 
As a
   result, <code>PyJWKClient.get_jwk_set()</code> returns the same 
<code>PyJWKSet</code> instance
   for as long as it stays cached, rather than a freshly built one per call in
   <code>[#1208](https://github.com/jpadilla/pyjwt/issues/1208) 
&lt;https://github.com/jpadilla/pyjwt/pull/1208&gt;</code>__</li>
   <li><code>PyJWKClient.fetch_data()</code> now raises
   <code>PyJWKClientError(&quot;The JWKS endpoint did not return a JSON 
object&quot;)</code> when
   the endpoint response is not a JSON object, instead of returning it for
   <code>get_jwk_set()</code> to reject. Callers reaching the JWKS through
   <code>get_jwk_set()</code> see the same error as before in
   <code>[#1208](https://github.com/jpadilla/pyjwt/issues/1208) 
&lt;https://github.com/jpadilla/pyjwt/pull/1208&gt;</code>__</li>
   </ul>
   <p>Fixed</p>
   <pre><code>
   - Return cached ``PyJWKSet`` values from ``PyJWKClient.get_jwk_set()`` 
instead
     of raising ``PyJWKClientError(&quot;The JWKS endpoint did not return a JSON
     object&quot;)``. ``JWKSetCache.put()`` documents ``PyJWKSet`` as the 
cached value,
     so callers pre-populating the cache to avoid a network round-trip could not
     read it back in `[#914](https://github.com/jpadilla/pyjwt/issues/914) 
&lt;https://github.com/jpadilla/pyjwt/issues/914&gt;`__ and
     `[#1208](https://github.com/jpadilla/pyjwt/issues/1208) 
&lt;https://github.com/jpadilla/pyjwt/pull/1208&gt;`__
   &lt;/tr&gt;&lt;/table&gt; 
   </code></pre>
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/7d5ef55e42ce42221f58dc49943e92ccad1fa66a";><code>7d5ef55</code></a>
 chore: prepare 2.15.1 release</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/7bf32526738fe837387bdedd4849a4a525c33a79";><code>7bf3252</code></a>
 Accept canonical Base64URL padding in JWT segments (<a 
href="https://redirect.github.com/jpadilla/pyjwt/issues/1216";>#1216</a>)</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/1d41a6478e1562e68ff667fcd703356acf085f68";><code>1d41a64</code></a>
 chore: prepare 2.15.0 release</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/9bc06658f875b9b40091539140bbbdc4639161c3";><code>9bc0665</code></a>
 fix: make recursive payload tests deterministic</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/5fde08a6cf906aa7698de2d6391d88b73006b17b";><code>5fde08a</code></a>
 fix: normalize recursive JWT payload errors</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/171062d2d734315272a901100aa4b109f2fc3c19";><code>171062d</code></a>
 utils: mention bytes in force_bytes type error (<a 
href="https://redirect.github.com/jpadilla/pyjwt/issues/1173";>#1173</a>)</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/c9d4d5375bf464ef363506fed9eb6e7f33217ab6";><code>c9d4d53</code></a>
 docs/conf: drop duplicate 'and' from read() docstring (<a 
href="https://redirect.github.com/jpadilla/pyjwt/issues/1174";>#1174</a>)</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/2763752196113e1473b0ed7905aa6034aedfbe53";><code>2763752</code></a>
 Add support for Python 3.15 (<a 
href="https://redirect.github.com/jpadilla/pyjwt/issues/1202";>#1202</a>)</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/4adcd02722f5011c60079d3978dfc167b9a8eaa5";><code>4adcd02</code></a>
 Catch http.client.HTTPException in PyJWKClient.fetch_data (<a 
href="https://redirect.github.com/jpadilla/pyjwt/issues/1201";>#1201</a>)</li>
   <li><a 
href="https://github.com/jpadilla/pyjwt/commit/9e501d993b4d3e7dba14bdb1722b1d993ac75097";><code>9e501d9</code></a>
 fix: correct docstring typo in _validate_jti (<a 
href="https://redirect.github.com/jpadilla/pyjwt/issues/1179";>#1179</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/jpadilla/pyjwt/compare/2.14.0...2.15.1";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyjwt&package-manager=pip&previous-version=2.14.0&new-version=2.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to