search

sonder-joker / mirai-compose

mirai-console的跨平台桌面端
140 stars 12 forks source link

Bump kotlinx-serialization-json from 1.1.0 to 1.2.1 #46

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps kotlinx-serialization-json from 1.1.0 to 1.2.1.

Release notes

Sourced from kotlinx-serialization-json's releases.

1.2.1

This release mainly contains bugfixes for various issues, including important broken thread-safety and improper encoding.

Features

  • Added support for nullable values, nested and empty collections in protobuf (#1430)

Bugfixes

  • Support @​JsonNames for enum values (#1473)
  • Handle EOF in skipElement correctly (#1475)
  • Allow using value classes with primitive carriers as map keys (#1470)
  • Read JsonNull only for non-string literals in JsonTreeReader (#1466)
  • Properly reuse JsonStringBuilders in CharArrayPool (#1455)
  • Properly ensure capacity of the string builder on the append slow-path (#1441)

1.2.0

This release has some known critical bugs, so we advise to use 1.2.1 instead.

This release contains a lot of new features and important improvements listed below; Kotlin 1.5.0 is used as a default compiler and language version.

JSON performance improvements

JSON encoder and decoder were revisited and significantly rewritten, which lead us to up to 2-3x times speedup in certain cases. Additional details can be found in the corresponding pull requests: [1], [2].

Ability to specify alternative names during JSON decoding

The one of the most voted issues is fixed now — it is possible to specify multiple names for one property using new @JsonNames annotation. Unlike @SerialName, it only affects JSON decoding, so it is useful when dealing with different versions of the API. We've prepared a documentation for you about it.

JsonConfiguration in public API

JsonConfiguration is exposed as a property of Json instance. You can use it to adjust behavior in your custom serializers. Check out more in the corresponding issue and the PR.

Generator for .proto files based on serializable Kotlin classes

Our implementation of Protocol Buffers format uses @Serializable Kotlin classes as a source of schema. This is very convenient for Kotlin-to-Kotlin communication, but makes interoperability between languages complicated. To resolve this issue, we now have a schema generator that can produce .proto files out of Kotlin classes. Using it, you can keep Kotlin classes as a source of truth and use traditional protoc compilers for other languages at the same time. To learn more, check out the documentation for the new ProtoBufSchemaGenerator class or visit the corresponding PR.

... (truncated)

Changelog

Sourced from kotlinx-serialization-json's changelog.

1.2.1 / 2021-05-14

This release mainly contains bugfixes for various issues, including important broken thread-safety and improper encoding.

Features

  • Added support for nullable values, nested and empty collections in protobuf (#1430)

Bugfixes

  • Support @​JsonNames for enum values (#1473)
  • Handle EOF in skipElement correctly (#1475)
  • Allow using value classes with primitive carriers as map keys (#1470)
  • Read JsonNull only for non-string literals in JsonTreeReader (#1466)
  • Properly reuse JsonStringBuilders in CharArrayPool (#1455)
  • Properly ensure capacity of the string builder on the append slow-path (#1441)

1.2.0 / 2021-04-27

This release has some known critical bugs, so we advise to use 1.2.1 instead.

This release contains a lot of new features and important improvements listed below; Kotlin 1.5.0 is used as a default compiler and language version.

JSON performance improvements

JSON encoder and decoder were revisited and significantly rewritten, which lead us to up to 2-3x times speedup in certain cases. Additional details can be found in the corresponding issues: [1], [2].

Ability to specify alternative names during JSON decoding

The one of the most voted issues is fixed now — it is possible to specify multiple names for one property using new @JsonNames annotation. Unlike @SerialName, it only affects JSON decoding, so it is useful when dealing with different versions of the API. We've prepared a documentation for you about it.

JsonConfiguration in public API

JsonConfiguration is exposed as a property of Json instance. You can use it to adjust behavior in your custom serializers. Check out more in the corresponding issue and the PR.

Generator for .proto files based on serializable Kotlin classes

Our implementation of Protocol Buffers format uses @Serializable Kotlin classes as a source of schema. This is very convenient for Kotlin-to-Kotlin communication, but makes interoperability between languages complicated. To resolve this issue, we now have a

... (truncated)

Commits
  • 61cc67e Prepare v1.2.1 release (#1478)
  • b9767c1 Ensure capacity os JsonStringBuilder on multi-symbol slowpath
  • a8af161 Merge remote-tracking branch 'origin/master' into dev
  • 8f82c6b Added support for nullable value, nested and empty collections in protobuf (#...
  • c0976fd Support @​JsonNames for enum values (#1473)
  • 2aa3a30 Handle EOF in skipElement correctly (#1475)
  • fcb641a Allow using value classes with primitive carriers as map keys without… (#1470)
  • 9338a72 Disable test for JS due to timeout restrictions
  • 23b3c8f Read JsonNull only for non-string literals in JsonTreeReader
  • a0a71ea Properly reuse JsonStringBuilders in CharArrayPool
  • Additional commits viewable in compare view


Dependabot compatibility score

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](https://app.dependabot.com): - 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)
dependabot-preview[bot] commented 3 years ago

Looks like org.jetbrains.kotlinx:kotlinx-serialization-json is no longer a dependency, so this is no longer needed.