dependabot[bot] opened a new pull request, #1587: URL: https://github.com/apache/cxf/pull/1587
Bumps `cxf.zipkin-reporter.version` from 2.17.0 to 2.17.1. Updates `io.zipkin.reporter2:zipkin-reporter-brave` from 2.17.0 to 2.17.1 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/RELEASE.md";>io.zipkin.reporter2:zipkin-reporter-brave's changelog</a>.</em></p> <blockquote> <h1>OpenZipkin Release Process</h1> <p>This repo uses semantic versions. Please keep this in mind when choosing version numbers.</p> <ol> <li> <p><strong>Alert others you are releasing</strong></p> <p>There should be no commits made to master while the release is in progress (about 10 minutes). Before you start a release, alert others on <a href="https://gitter.im/openzipkin/zipkin";>gitter</a> so that they don't accidentally merge anything. If they do, and the build fails because of that, you'll have to recreate the release tag described below.</p> </li> <li> <p><strong>Push a git tag</strong></p> <p>The trigger format is <code>release-MAJOR.MINOR.PATCH</code>, ex <code>git tag release-1.18.1 && git push origin release-1.18.1</code>.</p> </li> <li> <p><strong>Wait for CI</strong></p> <p>The <code>release-MAJOR.MINOR.PATCH</code> tag triggers <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_release";><code>https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_release</code></a>, which creates commits, <code>MAJOR.MINOR.PATCH</code> tag, and increments the version (maven-release-plugin).</p> <p>The <code>MAJOR.MINOR.PATCH</code> tag triggers <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/deploy";><code>https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/deploy</code></a>, which does the following:</p> <ul> <li>Publishes jars to <a href="https://oss.sonatype.org/content/repositories/releases";>https://oss.sonatype.org/content/repositories/releases</a> <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_deploy";><code>https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_deploy</code></a> <ul> <li>Later, the same jars synchronize to Maven Central</li> </ul> </li> </ul> <p>Notes:</p> <ul> <li><a href="https://search.maven.org/";>https://search.maven.org/</a> index will take longer than direct links like <a href="https://repo1.maven.org/maven2/io/zipkin";>https://repo1.maven.org/maven2/io/zipkin</a></li> </ul> </li> </ol> <h2>Credentials</h2> <p>The release process uses various credentials. If you notice something failing due to unauthorized, look at the notes in [.github/workflows/deploy.yml] and check the <a href="https://github.com/organizations/openzipkin/settings/secrets/actions";>org secrets</a>.</p> <h3>Troubleshooting invalid credentials</h3> <p>If you receive a '401 unauthorized' failure from OSSRH, it is likely <code>SONATYPE_USER</code> or <code>SONATYPE_PASSWORD</code> entries are invalid, or possibly the user associated with them does not have rights to upload.</p> <p>The least destructive test is to try to publish a snapshot manually. By passing the values CI would use, you can kick off a snapshot from your laptop. This is a good way to validate that your unencrypted credentials are authorized.</p> <p>Here's an example of a snapshot deploy with specified credentials.</p> <pre lang="bash"><code>$ export GPG_TTY=$(tty) && GPG_PASSPHRASE=whackamole SONATYPE_USER=adrianmole SONATYPE_PASSWORD=ed6f20bde9123bbb2312b221 build-bin/build-bin/maven/maven_deploy </code></pre> <h2>First release of the year</h2> <p>The license plugin verifies license headers of files include a copyright notice indicating the years a file was affected. This information is taken from git history. There's a once-a-year problem with files that include version numbers (pom.xml).</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/692bb3d681b889763eb79f72e2fc14b3619aa1ff";><code>692bb3d</code></a> [maven-release-plugin] prepare release 2.17.1</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/a2060beab9620ae609ca9dee35a42996c0668cb2";><code>a2060be</code></a> ci: adds action to test javadoc (<a href="https://redirect.github.com/openzipkin/zipkin-reporter-java/issues/230";>#230</a>)</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/66060b391732f46ad303a6f052e0a4bffec6ad8f";><code>66060b3</code></a> deps: updates to zipkin 2.25.2 (<a href="https://redirect.github.com/openzipkin/zipkin-reporter-java/issues/229";>#229</a>)</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/4e886ea2484ea29bf3801b9e2103b1ae3c1b8b85";><code>4e886ea</code></a> build: fixes animal-sniffer phase and runs on all JDKs (<a href="https://redirect.github.com/openzipkin/zipkin-reporter-java/issues/231";>#231</a>)</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/e635df871c16d83a7fc90543f7c6c0c6b3a872f4";><code>e635df8</code></a> [maven-release-plugin] prepare for next development iteration</li> <li>See full diff in <a href="https://github.com/openzipkin/zipkin-reporter-java/compare/2.17.0...2.17.1";>compare view</a></li> </ul> </details> <br /> Updates `io.zipkin.reporter2:zipkin-sender-urlconnection` from 2.17.0 to 2.17.1 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/RELEASE.md";>io.zipkin.reporter2:zipkin-sender-urlconnection's changelog</a>.</em></p> <blockquote> <h1>OpenZipkin Release Process</h1> <p>This repo uses semantic versions. Please keep this in mind when choosing version numbers.</p> <ol> <li> <p><strong>Alert others you are releasing</strong></p> <p>There should be no commits made to master while the release is in progress (about 10 minutes). Before you start a release, alert others on <a href="https://gitter.im/openzipkin/zipkin";>gitter</a> so that they don't accidentally merge anything. If they do, and the build fails because of that, you'll have to recreate the release tag described below.</p> </li> <li> <p><strong>Push a git tag</strong></p> <p>The trigger format is <code>release-MAJOR.MINOR.PATCH</code>, ex <code>git tag release-1.18.1 && git push origin release-1.18.1</code>.</p> </li> <li> <p><strong>Wait for CI</strong></p> <p>The <code>release-MAJOR.MINOR.PATCH</code> tag triggers <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_release";><code>https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_release</code></a>, which creates commits, <code>MAJOR.MINOR.PATCH</code> tag, and increments the version (maven-release-plugin).</p> <p>The <code>MAJOR.MINOR.PATCH</code> tag triggers <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/deploy";><code>https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/deploy</code></a>, which does the following:</p> <ul> <li>Publishes jars to <a href="https://oss.sonatype.org/content/repositories/releases";>https://oss.sonatype.org/content/repositories/releases</a> <a href="https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_deploy";><code>https://github.com/openzipkin/zipkin-reporter-java/blob/master/build-bin/maven/maven_deploy</code></a> <ul> <li>Later, the same jars synchronize to Maven Central</li> </ul> </li> </ul> <p>Notes:</p> <ul> <li><a href="https://search.maven.org/";>https://search.maven.org/</a> index will take longer than direct links like <a href="https://repo1.maven.org/maven2/io/zipkin";>https://repo1.maven.org/maven2/io/zipkin</a></li> </ul> </li> </ol> <h2>Credentials</h2> <p>The release process uses various credentials. If you notice something failing due to unauthorized, look at the notes in [.github/workflows/deploy.yml] and check the <a href="https://github.com/organizations/openzipkin/settings/secrets/actions";>org secrets</a>.</p> <h3>Troubleshooting invalid credentials</h3> <p>If you receive a '401 unauthorized' failure from OSSRH, it is likely <code>SONATYPE_USER</code> or <code>SONATYPE_PASSWORD</code> entries are invalid, or possibly the user associated with them does not have rights to upload.</p> <p>The least destructive test is to try to publish a snapshot manually. By passing the values CI would use, you can kick off a snapshot from your laptop. This is a good way to validate that your unencrypted credentials are authorized.</p> <p>Here's an example of a snapshot deploy with specified credentials.</p> <pre lang="bash"><code>$ export GPG_TTY=$(tty) && GPG_PASSPHRASE=whackamole SONATYPE_USER=adrianmole SONATYPE_PASSWORD=ed6f20bde9123bbb2312b221 build-bin/build-bin/maven/maven_deploy </code></pre> <h2>First release of the year</h2> <p>The license plugin verifies license headers of files include a copyright notice indicating the years a file was affected. This information is taken from git history. There's a once-a-year problem with files that include version numbers (pom.xml).</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/692bb3d681b889763eb79f72e2fc14b3619aa1ff";><code>692bb3d</code></a> [maven-release-plugin] prepare release 2.17.1</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/a2060beab9620ae609ca9dee35a42996c0668cb2";><code>a2060be</code></a> ci: adds action to test javadoc (<a href="https://redirect.github.com/openzipkin/zipkin-reporter-java/issues/230";>#230</a>)</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/66060b391732f46ad303a6f052e0a4bffec6ad8f";><code>66060b3</code></a> deps: updates to zipkin 2.25.2 (<a href="https://redirect.github.com/openzipkin/zipkin-reporter-java/issues/229";>#229</a>)</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/4e886ea2484ea29bf3801b9e2103b1ae3c1b8b85";><code>4e886ea</code></a> build: fixes animal-sniffer phase and runs on all JDKs (<a href="https://redirect.github.com/openzipkin/zipkin-reporter-java/issues/231";>#231</a>)</li> <li><a href="https://github.com/openzipkin/zipkin-reporter-java/commit/e635df871c16d83a7fc90543f7c6c0c6b3a872f4";><code>e635df8</code></a> [maven-release-plugin] prepare for next development iteration</li> <li>See full diff in <a href="https://github.com/openzipkin/zipkin-reporter-java/compare/2.17.0...2.17.1";>compare view</a></li> </ul> </details> <br /> 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: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
