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.

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

Update ktor to v2.3.9 #84

Merged
merged 1 commit into from
Mar 4, 2024
Merged

Update ktor to v2.3.9 #84

merged 1 commit into from
Mar 4, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 4, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.ktor:ktor-serialization-kotlinx-json 2.3.8 -> 2.3.9 age adoption passing confidence
io.ktor:ktor-client-cio 2.3.8 -> 2.3.9 age adoption passing confidence
io.ktor:ktor-client-core 2.3.8 -> 2.3.9 age adoption passing confidence
io.ktor:ktor-client-auth 2.3.8 -> 2.3.9 age adoption passing confidence

Release Notes

ktorio/ktor (io.ktor:ktor-serialization-kotlinx-json)

v2.3.9

Compare Source

Published 4 March 2024

Improvements
  • Allow to set secure cookie even with http scheme (KTOR-3159)
Bugfixes
  • ContentNegotiation: the plugin appends duplicated MIME type to Accept header (KTOR-6684)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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, check this box

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

@renovate renovate bot merged commit ca47afc into main Mar 4, 2024
1 check passed
@renovate renovate bot deleted the renovate/ktor branch March 4, 2024 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants