Update xmlserialization

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.github.pdvrieze.xmlutil:serialization-jvm	0.86.2 -> 0.90.3
io.github.pdvrieze.xmlutil:core-jvm	0.86.2 -> 0.86.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

pdvrieze/xmlutil (io.github.pdvrieze.xmlutil:serialization-jvm)

v0.90.3

Compare Source

Changes:

• In pedantic mode check that xml/xmlns are not used as names (they
  are always invalid). Note that namespaces can be specified using
  @XmlSerialName (for tags) and @XmlNamespaceDeclSpec (for
  additional names).
• The cache to use can now be configured. By default it uses the
  threadLocal version, but the thread unsafe default is also available,
  as is the FormatCache.Dummy cache that does no caching.
  Fixes:
• Fix support for multiple namespaces inside a single tag (QNameMap)
  as reported in #​249.
• Use threadlocals for caching document structures by default. This should avoid
  multithreading issues when reusing the format (recommended for speed)

v0.90.2

Compare Source

Changes:

• Update to Kotlin 2.0.21 / Kotlinx.serialization 1.7.3
• Add support for Android native targets (@​whyoleg in #​242)

v0.90.1

• Fix android plugin dependency.

v0.90.0

*(June 13, 2024)
Changes:

• The core module no longer automatically includes Android/Jvm "native"
  parsers by default, but uses the platform independent implementation.
  The Android/Jvm native parsers are available by including "core-jvm"
  and "core-android" packages. Note that serialization-jvm and
  serialization-android do so already.
• There is a coreCompat package that provides the original setup as
  direct replacement for core. This is a temporary package that will
  be removed at 1.0 release.

v0.86.3

*(December 14, 2023)
Changes:

• The XmlStreaming object in core is replaced by an interface IXmlStreaming
  with an accessor function xmlStreaming that provides an appropriate
  instance. The platform specific objects have been retained, but deprecated.
  In various places extension functions have been added.

Features:

• Update to kotlinx.serialization 1.6.1, add wasmJs/wasmWasi support.
• Support strict boolean parsing in policy
  (using xml schema rules allowing: 1, true, 0, false)
• Add an alias XmlBoolean that parses according to xml rules independent of
  the policy.
• Add versioned recommended configuration of the serializer. This provides
  for a stable configuration without manual configuration.
• Add support for purely text lists as text content (similar to attributes).
  This comes with a textListDelimiters policy function that allows
  specifying delimiters (note that it will apply xml schema compatible
  collapsing of whitespace - as articles do).

Fixes:

• Fix handling of empty textual value content.
• Fix collapsing whitespace when it is empty #​180.
• Fix the way the recommended config works to apply the policy. Note that
  recommended is not designed to be stable.
• Fix regression on root tag strictness. Now if the root type has a declared @XmlSerialName
  this type will be expected as the root tag unless explicitly specified differently
  as parameter.
• Add a proper non-deprecated constructor for DefaultXmlSerializationPolicy
  this takes a Builder, or a configuration lambda. Both options enable
  future proofing when further attributes are added.
• In the platform independent (native) DOM implementation allow
  comments outside the document element (rather than throwing an exception).
  Fixes #​189.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.