search

navikt / tiltakspenger-mottak

En tjeneste for tiltakspenger
MIT License
2 stars 0 forks source link

Bump ktorVersion from 2.3.6 to 2.3.7 #329

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 10 months ago

Bumps ktorVersion from 2.3.6 to 2.3.7. Updates io.ktor:ktor-client-content-negotiation-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-client-content-negotiation-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-client-content-negotiation-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-http-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-http-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-http-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-serialization-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-serialization-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-serialization-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-serialization-kotlinx-json-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-serialization-kotlinx-json-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-serialization-kotlinx-json-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-server-core-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-server-core-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-server-core-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-server-host-common-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-server-host-common-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-server-host-common-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-server-netty-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-server-netty-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-server-netty-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-utils-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-utils-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-utils-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-client-core-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-client-core-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-client-core-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-client-cio-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-client-cio-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-client-cio-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-client-mock-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-client-mock-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-client-mock-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


Updates io.ktor:ktor-server-test-host-jvm from 2.3.6 to 2.3.7

Release notes

Sourced from io.ktor:ktor-server-test-host-jvm's releases.

2.3.7

Published 7 December 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Changelog

Sourced from io.ktor:ktor-server-test-host-jvm's changelog.

2.3.7

Published 28 November 2023

Bugfixes

  • Server ContentNegotiation no longer allows multiple decoders for one Content-Type (KTOR-5410)
  • High Native Server Memory Usage (KTOR-6321)
  • WebSockets: Confusing error message when server doesn't respond with Upgrade (KTOR-6397)
  • ContentNegotiation: Adding charset to content type of JacksonConverter breaks request matching (KTOR-6420)
Commits


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 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)