Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump jjwt_version from 0.12.4 to 0.12.5 (#4011)
Bumps `jjwt_version` from 0.12.4 to 0.12.5. Updates `io.jsonwebtoken:jjwt-api` from 0.12.4 to 0.12.5 <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.5</h2> <p>This release fixes issue <a href="https://redirect.github.com/jwtk/jjwt/issues/916">#916</a> and ensures that builders' <code>NestedCollection</code> changes are applied to the collection immediately as mutation methods are called, no longer requiring application developers to call <code>.and()</code> to 'commit' or apply a change. For example, prior to this release, the following code did not apply changes:</p> <pre lang="java"><code>JwtBuilder builder = Jwts.builder(); builder.audience().add("an-audience"); // no .and() call builder.compact(); // would not keep 'an-audience' </code></pre> <p>Now this code works as expected and all other <code>NestedCollection</code> instances like it apply changes immediately (e.g. when calling <code>.add(value)</code>).</p> <p>However, standard fluent builder chains are still recommended for readability when feasible, e.g.</p> <pre lang="java"><code>Jwts.builder() .audience().add("an-audience").and() // allows fluent chaining .subject("Joe") // etc... .compact() </code></pre> <p>These same notes are repeated in the <a href="https://github.com/jwtk/jjwt/blob/0.12.5/CHANGELOG.md">CHANGELOG</a>, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.5/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> </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.5</h3> <p>This patch release:</p> <ul> <li> <p>Ensures that builders' <code>NestedCollection</code> changes are applied to the collection immediately as mutation methods are called, no longer requiring application developers to call <code>.and()</code> to 'commit' or apply a change. For example, prior to this release, the following code did not apply changes:</p> <pre lang="java"><code>JwtBuilder builder = Jwts.builder(); builder.audience().add("an-audience"); // no .and() call builder.compact(); // would not keep 'an-audience' </code></pre> <p>Now this code works as expected and all other <code>NestedCollection</code> instances like it apply changes immediately (e.g. when calling <code>.add(value)</code>).</p> <p>However, standard fluent builder chains are still recommended for readability when feasible, e.g.</p> <pre lang="java"><code>Jwts.builder() .audience().add("an-audience").and() // allows fluent chaining .subject("Joe") // etc... .compact() </code></pre> <p>See <a href="https://redirect.github.com/jwtk/jjwt/issues/916">Issue 916</a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jwtk/jjwt/commit/2399e2fdc5e20fad9d71d6bcbfd126cce6521638"><code>2399e2f</code></a> [maven-release-plugin] prepare release 0.12.5</li> <li><a href="https://github.com/jwtk/jjwt/commit/8d3de658357b351587df3790b3b1372944ad1f2f"><code>8d3de65</code></a> Preparing for 0.12.5 release</li> <li><a href="https://github.com/jwtk/jjwt/commit/a0a123e848fc25a7920bcbd84615f639c4cc098a"><code>a0a123e</code></a> PR <a href="https://redirect.github.com/jwtk/jjwt/issues/917">#917</a></li> <li><a href="https://github.com/jwtk/jjwt/commit/afcd88983252b249204d53830dd03884050b41af"><code>afcd889</code></a> 0.12.4 staging (<a href="https://redirect.github.com/jwtk/jjwt/issues/913">#913</a>)</li> <li>See full diff in <a href="https://github.com/jwtk/jjwt/compare/0.12.4...0.12.5">compare view</a></li> </ul> </details> <br /> Updates `io.jsonwebtoken:jjwt-impl` from 0.12.4 to 0.12.5 <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.5</h2> <p>This release fixes issue <a href="https://redirect.github.com/jwtk/jjwt/issues/916">#916</a> and ensures that builders' <code>NestedCollection</code> changes are applied to the collection immediately as mutation methods are called, no longer requiring application developers to call <code>.and()</code> to 'commit' or apply a change. For example, prior to this release, the following code did not apply changes:</p> <pre lang="java"><code>JwtBuilder builder = Jwts.builder(); builder.audience().add("an-audience"); // no .and() call builder.compact(); // would not keep 'an-audience' </code></pre> <p>Now this code works as expected and all other <code>NestedCollection</code> instances like it apply changes immediately (e.g. when calling <code>.add(value)</code>).</p> <p>However, standard fluent builder chains are still recommended for readability when feasible, e.g.</p> <pre lang="java"><code>Jwts.builder() .audience().add("an-audience").and() // allows fluent chaining .subject("Joe") // etc... .compact() </code></pre> <p>These same notes are repeated in the <a href="https://github.com/jwtk/jjwt/blob/0.12.5/CHANGELOG.md">CHANGELOG</a>, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.5/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> </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.5</h3> <p>This patch release:</p> <ul> <li> <p>Ensures that builders' <code>NestedCollection</code> changes are applied to the collection immediately as mutation methods are called, no longer requiring application developers to call <code>.and()</code> to 'commit' or apply a change. For example, prior to this release, the following code did not apply changes:</p> <pre lang="java"><code>JwtBuilder builder = Jwts.builder(); builder.audience().add("an-audience"); // no .and() call builder.compact(); // would not keep 'an-audience' </code></pre> <p>Now this code works as expected and all other <code>NestedCollection</code> instances like it apply changes immediately (e.g. when calling <code>.add(value)</code>).</p> <p>However, standard fluent builder chains are still recommended for readability when feasible, e.g.</p> <pre lang="java"><code>Jwts.builder() .audience().add("an-audience").and() // allows fluent chaining .subject("Joe") // etc... .compact() </code></pre> <p>See <a href="https://redirect.github.com/jwtk/jjwt/issues/916">Issue 916</a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jwtk/jjwt/commit/2399e2fdc5e20fad9d71d6bcbfd126cce6521638"><code>2399e2f</code></a> [maven-release-plugin] prepare release 0.12.5</li> <li><a href="https://github.com/jwtk/jjwt/commit/8d3de658357b351587df3790b3b1372944ad1f2f"><code>8d3de65</code></a> Preparing for 0.12.5 release</li> <li><a href="https://github.com/jwtk/jjwt/commit/a0a123e848fc25a7920bcbd84615f639c4cc098a"><code>a0a123e</code></a> PR <a href="https://redirect.github.com/jwtk/jjwt/issues/917">#917</a></li> <li><a href="https://github.com/jwtk/jjwt/commit/afcd88983252b249204d53830dd03884050b41af"><code>afcd889</code></a> 0.12.4 staging (<a href="https://redirect.github.com/jwtk/jjwt/issues/913">#913</a>)</li> <li>See full diff in <a href="https://github.com/jwtk/jjwt/compare/0.12.4...0.12.5">compare view</a></li> </ul> </details> <br /> Updates `io.jsonwebtoken:jjwt-jackson` from 0.12.4 to 0.12.5 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> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information
1 parent
9187da1
commit ff3b77c