Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update http4sversion to v1 (major) #79

Closed
wants to merge 1 commit into from
Closed

chore(deps): update http4sversion to v1 (major) #79

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 30, 2021 •
edited
Loading

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.http4s:http4s-blaze-client_2.13 (source) 0.22.0 -> 1.0-232-85dadc2 age adoption passing confidence
org.http4s:http4s-dsl_2.13 (source) 0.22.0 -> 1.0-232-85dadc2 age adoption passing confidence
org.http4s:http4s-blaze-server_2.13 (source) 0.22.0 -> 1.0-232-85dadc2 age adoption passing confidence

Release Notes

http4s/http4s

v0.23.10

This is a maintenance release, binary compatible with 0.23.x. It also includes merges of all the changes in 0.22.10.

Full Changelog: http4s/http4s@v0.23.9...v0.23.10

v0.23.9

This release is binary compatible with the 0.23.x series. It merges forward the changes of v0.22.10.

The signficant new feature is HTTP/2 support for Ember. Turn it on with a .withHttp2 on either the EmberClientBuilder or EmberServerBuilder.

Full Changelog: http4s/http4s@v0.23.8...v0.23.9

v0.23.8

This is a maintenance release, binary compatible with the 0.23.x series. It additionally includes a merge forward of the changes in v0.22.9.

Scala.js users must upgrade to at least 1.8.0 as of this release.

Full Changelog: http4s/http4s@v0.23.7...v0.23.8

v0.23.7

This is a maintenance release, binary compatible with the 0.23.x series. It additionally includes a merge forward of the changes in v0.22.8.

http4s-server and http4s-ember-server are now cross-built for the Scala.js platform.

Scala 3 users must upgrade to at least Scala 3.1.0 as of this release.

http4s-core
http4s-server
http4s-ember-server
Documentation
Behind the scenes
New Contributors

Full Changelog: http4s/http4s@v0.23.6...v0.23.7

v0.23.6

This is a routine maintenance release. It is binary compatible with the v0.23.x series and includes the changes in v0.22.7.

http4s-core
Noteworthy refactorings
  • #​5340: Replace our internal decode with FS2's decodeWithCharset. This only affects non-UTF-8 encodings.
http4s-client
Breaking changes
  • #​5348: Scala.js only: remove JavaNetClientBuilder. It already failed to link, and now it will fail to compile.
Bug fixes
  • #​5349: Fix deadlocks in Retry and FollowRedirect middlewares. We no longer attempt to acquire a second connection before releasing the first, potentially starving the connection pool.
Dependency updates
  • scalajs-1.7.1

v0.23.5

This is a maintenance release. It is binary compatible with 0.23.4, and includes the changes in 0.22.6.

Scala.js support is backported for a large subset of the modules present in 1.0.
Additional Scala.js-only modules for using http4s in the browser have been spun off as https://github.com/http4s/http4s-dom.

http4s-core
Cross Builds
Deprecations
  • #​5226: Migrate to the fs2.io.file APIs in EntityDecoder, StaticFile, and Part.
http4s-laws
Cross Builds
http4s-client
Cross Builds
http4s-server
Deprecations
  • #​5226: Migrate to the fs2.io.file APIs in FileService.
http4s-blaze-server
Bug fixes
  • #​5152: Pass a WebSocketBuilder, now named WebSocketBuilder2, when adding an HttpApp. This, combined with the new imapK method, lets web socket applications vary the local effect. Previously, this threw a ClassCastException.
http4s-blaze-client
Enhancements
  • #​5201: Adds an BlazeClientBuilder.apply method that uses the ExecutionContext from the Async[F] instance. The old constructor that required an explicit ExecutionContext is now deprecated. Users who need a custom ExecutionContext for blaze should call withExecutionContext.
http4s-ember-core
Cross Builds
http4s-ember-server
Bug fixes
  • #​5152: Pass a WebSocketBuilder, now named WebSocketBuilder2, when adding an HttpApp. This, combined with the new imapK method, lets web socket applications vary the local effect. Previously, this threw a ClassCastException.
Enhancements
  • #​5219: Add support for Unix sockets. This works on Linux and Darwin, but not on Windows. Use the new withUnixSocketConfig method on EmberServerBuilder to bind to an fs2.io.net.unixsocket.UnixSocketAddress.
http4s-ember-client
Cross Builds
Enhancements
  • #​5219: Add support for Unix sockets. This works on Linux and Darwin, but not on Windows. Use the new UnixSocket middleware to route requests to an fs2.io.net.unixsocket.UnixSocketAddress.
Dependency versions
  • fs2-3.1.4
  • ip4s-3.0.4

v0.23.4

This release includes security patches for GHSA-5vcm-3xc3-w7x3 for blaze-client, blaze-server, ember-client, ember-server, and jetty-client. It is binary compatible with v0.22.4, and forward-merges 0.22.5.

http4s-client
Enhancements
  • #​5190: Add an effect constructor for calculating effectual classifiers. Note that it is a mistake to consume the request body unless it is cached external to this call.
Dependency updates
  • cats-effect-3.2.8
  • fs2-3.1.2
  • keypool-0.4.7

v0.23.3

This is binary compatible with v0.23.2. It includes the fixes in v0.22.4.

http4s-ember-server
Bugfixes
  • #​5138: Correctly populate the SecureSession response attribute.

v0.23.2

This release includes a security patch to GHSA-52cf-226f-rhr6, along with all changes in v0.22.3.

This release is binary compatible with the 0.23 series.

http4s-core
Enhancements
  • #​5085: Make EntityEncoders for File, Path, and InputStream implicit. Since 0.23, they no longer require an explicit Blocker parameter, using Cats-Effect 3's runtime instead.
http4s-blaze-server
Bug fixes
  • #​5118: Don't block the TickWheelExecutor on cancellation. In-flight responses are canceled when a connection shuts down. If the response cancellation hangs, it blocks the TickWheelScheduler thread. When this thread blocks, subsequent scheduled events are not processed, and memory leaks with each newly scheduled event.
Enhancements
  • #​4782: Use Async[F].executionContext as a default ExecutionContext in BlazeServerBuilder.
http4s-ember-server
  • #​5106: Demote noisy WebSocket connection terminated with exception message to trace-level logging on broken pipes. This relies on exception message parsing and may not work well in all locales.
Dependency updates
  • cats-effect-3.2.5
  • fs2-3.1.1

v0.23.1

Includes all changes through v0.22.2.

Dependency updates
  • cats-effect-3.2.2
  • fs2-3.1.0
  • vault-3.0.4

v0.23.0

This is the first production release with Cats-Effect 3 support. All subsequent 0.23.x releases will be binary compatible with this.

Includes all changes through v0.22.1.

http4s-core
Breaking changes
  • #​4997: Refresh MimeDB from the IANA registry. It shuffles some constants in ways that offend MiMa, but you almost certainly won't notice.
Enhancements
  • #​4915: Add file-based multipart decoder with better resource handling. This deprecates the priod mixedMultipart decoder in favor of a mixedMultipartResource, which cleans up temporary storage on release of the resource. Please see the scaladoc for a usage example.
Various modules
Breaking changes
  • #​4998: Removes everything deprecated since 0.20.0, over 24 months and three breaking releases ago. See the pull request for a comprehensive list.
Refactoring
  • #​4986: Light refactoring of fs2 pipes in Ember and Blaze backends. Should not be visible.
Dependency updates
  • cats-effect-3.2.0
  • fs2-3.0.6
  • jawn-fs2-2.1.0
  • keypool-0.4.6

v0.22.11

This is a bugfix release, binary compatible with the 0.22.x series.

Full Changelog: http4s/http4s@v0.22.10...v0.22.11

v0.22.10

This release is focused on the client. The blaze-client is substantially refactored internally to improve resource safety. A new internal websocket client is published for implementation across repos. We expect to release this as a public API in the next release.

Full Changelog: http4s/http4s@v0.22.9...v0.22.10

v0.22.9

This release is binary compatible with 0.22.x series. The jawn upgrade mitigates CVE-2022-21653 out of the box for http4s-play-json.

Full Changelog: http4s/http4s@v0.22.8...v0.22.9

v0.22.8

This is a maintenance release, binary compatible with the 0.22.x series.

http4s-core
http4s-laws
Various backends
http4s-blaze-server
http4s-async-http-client
http4s-okhttp-client
http4s-jawn
http4s-scalatags
http4s-tomcat
Scalafixes
Documentation

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-http4sversion branch from a3e2879 to db3cf58 Compare December 9, 2021 10:53
@renovate renovate bot force-pushed the renovate/major-http4sversion branch from db3cf58 to 8b6273c Compare February 21, 2022 11:46
@renovate renovate bot force-pushed the renovate/major-http4sversion branch from 8b6273c to 39418a4 Compare February 27, 2022 10:35
@mi-char mi-char closed this Mar 4, 2022
@mi-char mi-char deleted the renovate/major-http4sversion branch March 4, 2022 08:44
@renovate
Copy link
Contributor Author

renovate bot commented Mar 4, 2022

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 1.x releases. However, if you upgrade to 1.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mi-char @renovate-bot