You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@streampipes.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2023/10/16 02:42:20 UTC

[PR] chore(deps): bump jjwt.version from 0.11.2 to 0.12.3

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

   Bumps `jjwt.version` from 0.11.2 to 0.12.3.
   Updates `io.jsonwebtoken:jjwt-api` from 0.11.2 to 0.12.3
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/releases">io.jsonwebtoken:jjwt-api's releases</a>.</em></p>
   <blockquote>
   <h2>0.12.3</h2>
   <p>This is a minor patch release that address two issues:</p>
   <ol>
   <li>
   <p>The <code>org.json</code> dependency has been upgraded to <code>20231013</code> to address that library's
   <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5072">CVE-2023-5072</a> vulnerability.</p>
   </li>
   <li>
   <p>Empty custom claims values are (re-)enabled which was the behavior in &lt;= 0.11.5. See <a href="https://redirect.github.com/jwtk/jjwt/issues/858">Issue 858</a>.</p>
   </li>
   </ol>
   <p>These same notes are repeated in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/CHANGELOG.md">CHANGELOG</a>, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/README.md">README</a>.</p>
   <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p>
   <h2>0.12.2</h2>
   <p>This is a follow-up release to finalize the work in <code>0.12.1</code> that tried to fix a reflection scope problem
   on &gt;= JDK 17.  The 0.12.1 fix worked, but only if the importing project or application did <em>not</em> have its own
   <code>module-info.java</code> file.</p>
   <p>This release removes that reflection code entirely in favor of a JJWT-native implementation, eliminating JPMS
   module (scope) problems on &gt;= JDK 17. As such, <code>--add-opens</code> flags are no longer required to use JJWT.</p>
   <p>The fix has been tested up through JDK 21 in a separate application environment (out of JJWT's codebase) to assert
   expected functionality in a 'clean room' environment in a project both with and without <code>module-info.java</code> usage.</p>
   <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/CHANGELOG.md">CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/README.md">README</a>.</p>
   <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p>
   <h2>0.12.1</h2>
   <p>This is a quick follow-up release from yesterday's <code>0.12.0</code> release that addresses a reflection issue on JDK 17.  The fix has been tested up through JDK 21.</p>
   <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/CHANGELOG.md">CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/README.md">README</a>.</p>
   <p>Please allow 30 minutes for the release to be available in Maven Central.</p>
   <h2>0.12.0</h2>
   <p>It is finally here!  This release includes full support for JSON Web Encryption (JWE), JSON Web Keys (JWK), JSON Web Key Thumbprints, JSON Web Key Thumbprint URIs, and so, so much more.</p>
   <p>This is the culmination of <em>hundreds</em> of hours worth of work and testing, and we're glad to <em>finally</em> release it.  However, please note:</p>
   <p><strong>This is our first-ever breaking change release.</strong>  While we tried hard to minimize the breakages, some were just necessary in preparation for 1.0 and to finalize all JWT RFC features.  <strong>If you are not partial to fixing changes when upgrading a library, we strongly encourage you to wait until the 1.0 release.</strong></p>
   <p>Please pay particular attention to the <a href="https://github.com/jwtk/jjwt/blob/0.12.0/CHANGELOG.md">CHANGELOG</a> listing breaking changes.</p>
   <p>Full documentation is available in the <a href="https://github.com/jwtk/jjwt/blob/0.12.0/README.md">README</a>.</p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/blob/master/CHANGELOG.md">io.jsonwebtoken:jjwt-api's changelog</a>.</em></p>
   <blockquote>
   <h3>0.12.3</h3>
   <p>This patch release:</p>
   <ul>
   <li>Upgrades the <code>org.json</code> dependency to <code>20231013</code> to address that library's
   <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5072">CVE-2023-5072</a> vulnerability.</li>
   <li>(Re-)enables empty values for custom claims, which was the behavior in &lt;= 0.11.5.
   <a href="https://redirect.github.com/jwtk/jjwt/issues/858">Issue 858</a>.</li>
   </ul>
   <h3>0.12.2</h3>
   <p>This is a follow-up release to finalize the work in 0.12.1 that tried to fix a reflection scope problem
   on &gt;= JDK 17.  The 0.12.1 fix worked, but only if the importing project or application did <em>not</em> have its own
   <code>module-info.java</code> file.</p>
   <p>This release removes that reflection code entirely in favor of a JJWT-native implementation, eliminating JPMS
   module (scope) problems on &gt;= JDK 17. As such, <code>--add-opens</code> flags are no longer required to use JJWT.</p>
   <p>The fix has been tested up through JDK 21 in a separate application environment (out of JJWT's codebase) to assert
   expected functionality in a 'clean room' environment in a project both with and without <code>module-info.java</code> usage.</p>
   <h3>0.12.1</h3>
   <p>Enabled reflective access on JDK 17+ to <code>java.io.ByteArrayInputStream</code> and <code>sun.security.util.KeyUtil</code> for
   <code>jjwt-impl.jar</code></p>
   <h3>0.12.0</h3>
   <p>This is a big release! JJWT now fully supports Encrypted JSON Web Tokens (JWE), JSON Web Keys (JWK) and more!  See the
   sections below enumerating all new features as well as important notes on breaking changes or backwards-incompatible
   changes made in preparation for the upcoming 1.0 release.</p>
   <p><strong>Because breaking changes are being introduced, it is strongly recommended to wait until the upcoming 1.0 release
   where you can address breaking changes one time only</strong>.</p>
   <p>Those that need immediate JWE encryption and JWK key support
   however will likely want to upgrade now and deal with the smaller subset of breaking changes in the 1.0 release.</p>
   <h4>Simplified Starter Jar</h4>
   <p>Those upgrading to new modular JJWT versions from old single-jar versions will transparently obtain everything
   they need in their Maven, Gradle or Android projects.</p>
   <p>JJWT's early releases had one and only one .jar: <code>jjwt.jar</code>.  Later releases moved to a modular design with 'api' and
   'impl' jars including 'plugin' jars for Jackson, GSON, org.json, etc.  Some users upgrading from the earlier single
   jar to JJWT's later versions have been frustrated by being forced to learn how to configure the more modular .jars.</p>
   <p>This release re-introduces the <code>jjwt.jar</code> artifact again, but this time it is simply an empty .jar with Maven
   metadata that will automatically transitively download the following into a project, retaining the old single-jar
   behavior:</p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a href="https://github.com/jwtk/jjwt/commit/d4a0827071b8682f4443313a6e948a0619668dda"><code>d4a0827</code></a> [maven-release-plugin] prepare release 0.12.3</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/bc540fc7ec9eec661af8fff8f18c326429e424ad"><code>bc540fc</code></a> Version reference changes in preparation for the 0.12.3 release</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/28a2ca716a24df4e1eb8bc1c0efc85743742d909"><code>28a2ca7</code></a> Upgraded org.json dependency to 20231013</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/db339704e5bb4662c0e25a3f3a2abe2d155189e1"><code>db33970</code></a> Custom empty claims</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/59c9df123183608fb798edabe8fb2fdcb746fa32"><code>59c9df1</code></a> Released 0.12.2 (<a href="https://redirect.github.com/jwtk/jjwt/issues/856">#856</a>)</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/a7d3d3197ca046623b4e3cf979e64fdf94eef1b1"><code>a7d3d31</code></a> 854 jdk17 visibility (<a href="https://redirect.github.com/jwtk/jjwt/issues/855">#855</a>)</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/fad6e2737d08d1861925416bc79790f2e29eab52"><code>fad6e27</code></a> Released 0.12.1</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/1625067b85680733d275eba86ad46a0d222425a2"><code>1625067</code></a> Closes <a href="https://redirect.github.com/jwtk/jjwt/issues/849">#849</a> (<a href="https://redirect.github.com/jwtk/jjwt/issues/852">#852</a>)</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/44cd5523e890c99451682268c7dac951ccd96a18"><code>44cd552</code></a> Update README.md</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/0c3040922a43160c071d8e838d9deec51e88f408"><code>0c30409</code></a> 0.12.0 staging complete (<a href="https://redirect.github.com/jwtk/jjwt/issues/847">#847</a>)</li>
   <li>Additional commits viewable in <a href="https://github.com/jwtk/jjwt/compare/0.11.2...0.12.3">compare view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.jsonwebtoken:jjwt-impl` from 0.11.2 to 0.12.3
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/releases">io.jsonwebtoken:jjwt-impl's releases</a>.</em></p>
   <blockquote>
   <h2>0.12.3</h2>
   <p>This is a minor patch release that address two issues:</p>
   <ol>
   <li>
   <p>The <code>org.json</code> dependency has been upgraded to <code>20231013</code> to address that library's
   <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5072">CVE-2023-5072</a> vulnerability.</p>
   </li>
   <li>
   <p>Empty custom claims values are (re-)enabled which was the behavior in &lt;= 0.11.5. See <a href="https://redirect.github.com/jwtk/jjwt/issues/858">Issue 858</a>.</p>
   </li>
   </ol>
   <p>These same notes are repeated in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/CHANGELOG.md">CHANGELOG</a>, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/README.md">README</a>.</p>
   <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p>
   <h2>0.12.2</h2>
   <p>This is a follow-up release to finalize the work in <code>0.12.1</code> that tried to fix a reflection scope problem
   on &gt;= JDK 17.  The 0.12.1 fix worked, but only if the importing project or application did <em>not</em> have its own
   <code>module-info.java</code> file.</p>
   <p>This release removes that reflection code entirely in favor of a JJWT-native implementation, eliminating JPMS
   module (scope) problems on &gt;= JDK 17. As such, <code>--add-opens</code> flags are no longer required to use JJWT.</p>
   <p>The fix has been tested up through JDK 21 in a separate application environment (out of JJWT's codebase) to assert
   expected functionality in a 'clean room' environment in a project both with and without <code>module-info.java</code> usage.</p>
   <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/CHANGELOG.md">CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/README.md">README</a>.</p>
   <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p>
   <h2>0.12.1</h2>
   <p>This is a quick follow-up release from yesterday's <code>0.12.0</code> release that addresses a reflection issue on JDK 17.  The fix has been tested up through JDK 21.</p>
   <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/CHANGELOG.md">CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/README.md">README</a>.</p>
   <p>Please allow 30 minutes for the release to be available in Maven Central.</p>
   <h2>0.12.0</h2>
   <p>It is finally here!  This release includes full support for JSON Web Encryption (JWE), JSON Web Keys (JWK), JSON Web Key Thumbprints, JSON Web Key Thumbprint URIs, and so, so much more.</p>
   <p>This is the culmination of <em>hundreds</em> of hours worth of work and testing, and we're glad to <em>finally</em> release it.  However, please note:</p>
   <p><strong>This is our first-ever breaking change release.</strong>  While we tried hard to minimize the breakages, some were just necessary in preparation for 1.0 and to finalize all JWT RFC features.  <strong>If you are not partial to fixing changes when upgrading a library, we strongly encourage you to wait until the 1.0 release.</strong></p>
   <p>Please pay particular attention to the <a href="https://github.com/jwtk/jjwt/blob/0.12.0/CHANGELOG.md">CHANGELOG</a> listing breaking changes.</p>
   <p>Full documentation is available in the <a href="https://github.com/jwtk/jjwt/blob/0.12.0/README.md">README</a>.</p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/blob/master/CHANGELOG.md">io.jsonwebtoken:jjwt-impl's changelog</a>.</em></p>
   <blockquote>
   <h3>0.12.3</h3>
   <p>This patch release:</p>
   <ul>
   <li>Upgrades the <code>org.json</code> dependency to <code>20231013</code> to address that library's
   <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5072">CVE-2023-5072</a> vulnerability.</li>
   <li>(Re-)enables empty values for custom claims, which was the behavior in &lt;= 0.11.5.
   <a href="https://redirect.github.com/jwtk/jjwt/issues/858">Issue 858</a>.</li>
   </ul>
   <h3>0.12.2</h3>
   <p>This is a follow-up release to finalize the work in 0.12.1 that tried to fix a reflection scope problem
   on &gt;= JDK 17.  The 0.12.1 fix worked, but only if the importing project or application did <em>not</em> have its own
   <code>module-info.java</code> file.</p>
   <p>This release removes that reflection code entirely in favor of a JJWT-native implementation, eliminating JPMS
   module (scope) problems on &gt;= JDK 17. As such, <code>--add-opens</code> flags are no longer required to use JJWT.</p>
   <p>The fix has been tested up through JDK 21 in a separate application environment (out of JJWT's codebase) to assert
   expected functionality in a 'clean room' environment in a project both with and without <code>module-info.java</code> usage.</p>
   <h3>0.12.1</h3>
   <p>Enabled reflective access on JDK 17+ to <code>java.io.ByteArrayInputStream</code> and <code>sun.security.util.KeyUtil</code> for
   <code>jjwt-impl.jar</code></p>
   <h3>0.12.0</h3>
   <p>This is a big release! JJWT now fully supports Encrypted JSON Web Tokens (JWE), JSON Web Keys (JWK) and more!  See the
   sections below enumerating all new features as well as important notes on breaking changes or backwards-incompatible
   changes made in preparation for the upcoming 1.0 release.</p>
   <p><strong>Because breaking changes are being introduced, it is strongly recommended to wait until the upcoming 1.0 release
   where you can address breaking changes one time only</strong>.</p>
   <p>Those that need immediate JWE encryption and JWK key support
   however will likely want to upgrade now and deal with the smaller subset of breaking changes in the 1.0 release.</p>
   <h4>Simplified Starter Jar</h4>
   <p>Those upgrading to new modular JJWT versions from old single-jar versions will transparently obtain everything
   they need in their Maven, Gradle or Android projects.</p>
   <p>JJWT's early releases had one and only one .jar: <code>jjwt.jar</code>.  Later releases moved to a modular design with 'api' and
   'impl' jars including 'plugin' jars for Jackson, GSON, org.json, etc.  Some users upgrading from the earlier single
   jar to JJWT's later versions have been frustrated by being forced to learn how to configure the more modular .jars.</p>
   <p>This release re-introduces the <code>jjwt.jar</code> artifact again, but this time it is simply an empty .jar with Maven
   metadata that will automatically transitively download the following into a project, retaining the old single-jar
   behavior:</p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a href="https://github.com/jwtk/jjwt/commit/d4a0827071b8682f4443313a6e948a0619668dda"><code>d4a0827</code></a> [maven-release-plugin] prepare release 0.12.3</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/bc540fc7ec9eec661af8fff8f18c326429e424ad"><code>bc540fc</code></a> Version reference changes in preparation for the 0.12.3 release</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/28a2ca716a24df4e1eb8bc1c0efc85743742d909"><code>28a2ca7</code></a> Upgraded org.json dependency to 20231013</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/db339704e5bb4662c0e25a3f3a2abe2d155189e1"><code>db33970</code></a> Custom empty claims</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/59c9df123183608fb798edabe8fb2fdcb746fa32"><code>59c9df1</code></a> Released 0.12.2 (<a href="https://redirect.github.com/jwtk/jjwt/issues/856">#856</a>)</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/a7d3d3197ca046623b4e3cf979e64fdf94eef1b1"><code>a7d3d31</code></a> 854 jdk17 visibility (<a href="https://redirect.github.com/jwtk/jjwt/issues/855">#855</a>)</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/fad6e2737d08d1861925416bc79790f2e29eab52"><code>fad6e27</code></a> Released 0.12.1</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/1625067b85680733d275eba86ad46a0d222425a2"><code>1625067</code></a> Closes <a href="https://redirect.github.com/jwtk/jjwt/issues/849">#849</a> (<a href="https://redirect.github.com/jwtk/jjwt/issues/852">#852</a>)</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/44cd5523e890c99451682268c7dac951ccd96a18"><code>44cd552</code></a> Update README.md</li>
   <li><a href="https://github.com/jwtk/jjwt/commit/0c3040922a43160c071d8e838d9deec51e88f408"><code>0c30409</code></a> 0.12.0 staging complete (<a href="https://redirect.github.com/jwtk/jjwt/issues/847">#847</a>)</li>
   <li>Additional commits viewable in <a href="https://github.com/jwtk/jjwt/compare/0.11.2...0.12.3">compare view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.jsonwebtoken:jjwt-jackson` from 0.11.2 to 0.12.3
   
   
   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 merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
   - `@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: commits-unsubscribe@streampipes.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] chore(deps): bump jjwt.version from 0.11.2 to 0.12.3

Posted by "bossenti (via GitHub)" <gi...@apache.org>.
bossenti closed pull request #2028: chore(deps): bump jjwt.version from 0.11.2 to 0.12.3
URL: https://github.com/apache/streampipes/pull/2028


-- 
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: dev-unsubscribe@streampipes.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] chore(deps): bump jjwt.version from 0.11.2 to 0.12.3

Posted by "dependabot[bot] (via GitHub)" <gi...@apache.org>.
dependabot[bot] commented on PR #2028:
URL: https://github.com/apache/streampipes/pull/2028#issuecomment-1763733167

   OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts on it.


-- 
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: commits-unsubscribe@streampipes.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org