Bump reactor-netty from 0.9.4.RELEASE to 0.9.5.RELEASE

[dependabot-preview]

Bumps reactor-netty from 0.9.4.RELEASE to 0.9.5.RELEASE.

Release notes

Sourced from reactor-netty's releases.

v0.9.5.RELEASE

Reactor Netty 0.9.5.RELEASE is part of Dysprosium-SR5 Release Train.

This is a recommended update for all Reactor Netty 0.9.x users.

See also release notes from 0.8.16 for changes that were inherited from the 0.8.x maintenance release.

⚠️ Update considerations and deprecations

• ConnectionProvider#builder is the new way for creating ConnectionProvider. The old methods for creating ConnectionProvider are deprecated, they use the new functionality in a backwards compatible way. Notes:

  • max pending acquire configuration is unbounded for the deprecated methods, but has a limit if the new API is used directly.
  • all new configurations will be available only when using the new API.

• WebsocketServerSpec is the new way for configuring websocket on the server. The old methods for configuration are deprecated, they use the new functionality in a backwards compatible way.

• Metrics

  • ConnectionProvider metrics name reactor.netty.connection.provider.<name> is deprecated. The new name is reactor.netty.connection.provider with tag name.
  • ByteBufAllocator metrics name reactor.netty.<type>.bytebuf.allocator is deprecated. The new name is reactor.netty.bytebuf.allocator with tag type.

✨ New features and improvements

• Depending on Reactor Core v3.3.3.RELEASE, see release notes (aa9b1d43b0ba5fab8b4d088eb06835785ea5d77d)
• ConnectionProvider configuration
  • Add API for enabling metrics for the ConnectionProvider. HttpClient#metrics invocation enables the metrics for the HttpClient which includes the metrics for the ConnectionProvider. This new API enables ONLY the metrics for the ConnectionProvider. (#925, d4b948c8f37d0d1ab0c0dee70fdb2f8453f351e2)
  • Add ConnectionProvider#builder. (#933, #954, 25acabf62ec886038d5f9504f8e190345bf0df78)
  • Add System properties for connection pool - max idle time and leasing strategy. (#938, #1011)
  • Add API for configuring max pending acquire requests. (#951, #957, a976a6e7dd382ada9abe1de8789903eb2ca58970)
  • Deprecate the methods for creating ConnectionProvider in favour of ConnectionProvider#builder. (#955, #956, 71af605daf5d6b8d41060725d64edb351e6c048a)
  • Add configuration for switching between FIFO and LIFO order for the channels in the pool. (#962, #963)
  • ConnectionProvider API refinements. Pending acquire max count will not be unbounded for the new functionality. (#966)
  • Clarify that maxConnections is per single connection pool. The connection pool corresponds to a concrete remote host. (09f79c2e850e40fdd0d19bc04a82089b838b9769)
  • Add connection pool configuration per remote host. (#973, #1007)
• WebSocket server configuration
  • Add builder for configuring WebSocket. (#958, #959, 643ba24f73286edcc1e4dbdf4fb38fdeacd2e507)
  • Separate HTTP and WebSocket compression configuration. (#970, #980)
  • Add separate builder for Websocket server configuration. (#1009, fafc2e9dc86979566f751964597b0ad0e0816f83)
• Metrics
  • Remove maximum allowable tags configuration for the metrics. As Micrometer global composite repository is used Reactor Netty users can configure maximum allowable tags outside of Reactor Netty. (#950, #985, 800f7855bb6569d3da1bbaa72c6ab647be0d6fcc)
  • ConnectionProvider metrics set the pool name in a tag and not in the metric name. New name is reactor.netty.connection.provider and the tag name is name. (#986, #987, afd39e4d2533d46aa02e6200907335fba7a8b6e1, e2121c31a887adb8e4f05c14525c434e293df598)
  • Deprecate the old ConnectionProvider metrics name - reactor.netty.connection.provider.<name>. (9984e4c691d0676ffcd5135676fb8a1c44d5cccc)
  • Revise metrics public constants. Add javadoc. (69ac2d5607282f3e95320f40ce6f12362790792a)
  • ByteBufAllocator metrics set the alloc type in a tag and not in the metric name. New name is reactor.netty.bytebuf.allocator and the tag name is type. Deprecate the old name reactor.netty.<type>.bytebuf.allocator. (f8ed0bc2f1c2928beda917f07326c24c0aac01cb)
• Add HttpClient#doAfterResponseSuccess that will be triggered only when the response is fully received. Revise javadoc for HttpClient#doOn* methods. Deprecate HttpClient#doAfterResponse. (#975, #978)

🪲 Bug fixes

• Ensure the actual request data is available when HttpClient#doOnRequest. (#994, #997, #998, 40552bc52b97aea79acdfa31b30cc91ece494964)
• Clean up channel pipeline when H2C and HTTP11 support. (1f22b7fd3f6ad48a7203e883b80428590cb5bd00)

📖 Documentation, Tests and Build

• Fix timing issue. (248b5aa117317b817a32f1b52ecb92cb0c80e002)
• Fixed imports. (#993)

... (truncated)

Commits

• 64cb297 [artifactory-release] Release version 0.9.5.RELEASE
• aa9b1d4 Prepare release 0.9.5.RELEASE
• 70155cc Merge (ignore) 0.8.x release into 0.9.x
• de7961e Back to core 3.2.16 snapshots
• 0a7d12e [artifactory-release] Next development version 0.8.17.BUILD-SNAPSHOT
• 3ee2404 [artifactory-release] Release version 0.8.16.RELEASE
• 603487b Prepare release 0.8.16.RELEASE
• a68ac6e Add System properties for connection pool - max idle time and leasing strategy
• 303f3bb Merge branch '0.8.x' into 0.9.x
• dfb71cf Fix NPE when request with CONNECT method
• 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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)