Bump brave.version from 5.16.0 to 5.17.0

[dependabot]

Bumps brave.version from 5.16.0 to 5.17.0.
Updates io.zipkin.brave:brave from 5.16.0 to 5.17.0

Changelog

Sourced from io.zipkin.brave:brave's changelog.

OpenZipkin Release Process

This repo uses semantic versions. Please keep this in mind when choosing version numbers.

1. Alert others you are releasing

   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 gitter 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.

2. Push a git tag

   The trigger format is release-MAJOR.MINOR.PATCH, ex git tag release-1.18.1 && git push origin release-1.18.1.

3. Wait for CI

   The release-MAJOR.MINOR.PATCH tag triggers https://github.com/openzipkin/brave/blob/master/build-bin/maven/maven_release, which creates commits, MAJOR.MINOR.PATCH tag, and increments the version (maven-release-plugin).

   The MAJOR.MINOR.PATCH tag triggers https://github.com/openzipkin/brave/blob/master/build-bin/deploy, which does the following:

   • Publishes jars to https://oss.sonatype.org/content/repositories/releases https://github.com/openzipkin/brave/blob/master/build-bin/maven/maven_deploy
     • Later, the same jars synchronize to Maven Central
   • Publishes Javadoc to https://zipkin.io/brave into a versioned subdirectory

   Notes:

   • https://search.maven.org/ index will take longer than direct links like https://repo1.maven.org/maven2/io/zipkin

Credentials

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 org secrets.

Troubleshooting invalid credentials

If you receive a '401 unauthorized' failure from OSSRH, it is likely SONATYPE_USER or SONATYPE_PASSWORD entries are invalid, or possibly the user associated with them does not have rights to upload.

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.

Here's an example of a snapshot deploy with specified credentials.

$ export GPG_TTY=$(tty) && GPG_PASSPHRASE=whackamole SONATYPE_USER=adrianmole SONATYPE_PASSWORD=ed6f20bde9123bbb2312b221 build-bin/build-bin/maven/maven_deploy

First release of the year

The license plugin verifies license headers of files include a copyright notice indicating the years a file was affected.

... (truncated)

Commits

• d55db97 [maven-release-plugin] prepare release 5.17.0
• 053e743 deps: updates to zipkin-reporter 2.17.1 (#1390)
• 90537d6 build: fixes animal-sniffer phase and runs on all JDKs (#1389)
• 677244a fix compiler
• 2bde4fe [maven-release-plugin] prepare for next development iteration
• c204053 [maven-release-plugin] prepare release 5.17.0
• 20692fe deps: bumps all main versions that compile (#1388)
• b0ad9aa Migrates all tests and fixtures from JUnit 4.x to Jupiter (#1387)
• 902e560 dubbo: updates dependencies to latest versions (#1386)
• eac0ffa build: updates to build and test with LTS JDKs (#1385)
• Additional commits viewable in compare view

Updates io.zipkin.brave:brave-context-slf4j from 5.16.0 to 5.17.0

Updates io.zipkin.brave:brave-instrumentation-jaxrs2 from 5.16.0 to 5.17.0

Updates io.zipkin.brave:brave-instrumentation-servlet from 5.16.0 to 5.17.0

Updates io.zipkin.brave:brave-instrumentation-spring-web from 5.16.0 to 5.17.0

Updates io.zipkin.brave:brave-instrumentation-spring-webmvc from 5.16.0 to 5.17.0

Updates io.zipkin.brave:brave-spring-beans from 5.16.0 to 5.17.0

Changelog

Sourced from io.zipkin.brave:brave-spring-beans's changelog.

OpenZipkin Release Process

This repo uses semantic versions. Please keep this in mind when choosing version numbers.

1. Alert others you are releasing

   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 gitter 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.

2. Push a git tag

   The trigger format is release-MAJOR.MINOR.PATCH, ex git tag release-1.18.1 && git push origin release-1.18.1.

3. Wait for CI

   The release-MAJOR.MINOR.PATCH tag triggers https://github.com/openzipkin/brave/blob/master/build-bin/maven/maven_release, which creates commits, MAJOR.MINOR.PATCH tag, and increments the version (maven-release-plugin).

   The MAJOR.MINOR.PATCH tag triggers https://github.com/openzipkin/brave/blob/master/build-bin/deploy, which does the following:

   • Publishes jars to https://oss.sonatype.org/content/repositories/releases https://github.com/openzipkin/brave/blob/master/build-bin/maven/maven_deploy
     • Later, the same jars synchronize to Maven Central
   • Publishes Javadoc to https://zipkin.io/brave into a versioned subdirectory

   Notes:

   • https://search.maven.org/ index will take longer than direct links like https://repo1.maven.org/maven2/io/zipkin

Credentials

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 org secrets.

Troubleshooting invalid credentials

If you receive a '401 unauthorized' failure from OSSRH, it is likely SONATYPE_USER or SONATYPE_PASSWORD entries are invalid, or possibly the user associated with them does not have rights to upload.

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.

Here's an example of a snapshot deploy with specified credentials.

$ export GPG_TTY=$(tty) && GPG_PASSPHRASE=whackamole SONATYPE_USER=adrianmole SONATYPE_PASSWORD=ed6f20bde9123bbb2312b221 build-bin/build-bin/maven/maven_deploy

First release of the year

The license plugin verifies license headers of files include a copyright notice indicating the years a file was affected.

... (truncated)

Commits

• d55db97 [maven-release-plugin] prepare release 5.17.0
• 053e743 deps: updates to zipkin-reporter 2.17.1 (#1390)
• 90537d6 build: fixes animal-sniffer phase and runs on all JDKs (#1389)
• 677244a fix compiler
• 2bde4fe [maven-release-plugin] prepare for next development iteration
• c204053 [maven-release-plugin] prepare release 5.17.0
• 20692fe deps: bumps all main versions that compile (#1388)
• b0ad9aa Migrates all tests and fixtures from JUnit 4.x to Jupiter (#1387)
• 902e560 dubbo: updates dependencies to latest versions (#1386)
• eac0ffa build: updates to build and test with LTS JDKs (#1385)
• Additional commits viewable in compare view

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 commands and options

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)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1d55d7d) 44.35% compared to head (549742b) 44.25%.

❗ Current head 549742b differs from pull request most recent head 75fb98d. Consider uploading reports for the commit 75fb98d to get more accurate results

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #4143      +/-   ##
============================================
- Coverage     44.35%   44.25%   -0.11%     
+ Complexity     5395     5381      -14     
============================================
  Files          1384     1384              
  Lines         34331    34331              
  Branches       3325     3325              
============================================
- Hits          15229    15192      -37     
- Misses        17868    17906      +38     
+ Partials       1234     1233       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.