chore(deps): bump xmlutil from 1.0.0-rc2 to 1.0.0-rc3

[dependabot]

Bumps xmlutil from 1.0.0-rc2 to 1.0.0-rc3.
Updates io.github.pdvrieze.xmlutil:core from 1.0.0-rc2 to 1.0.0-rc3

Release notes

Sourced from io.github.pdvrieze.xmlutil:core's releases.

1.0.0-rc3 – The full DOM

Features:

• There is now a common DOM implementation on all platforms that cooperates with the platform's DOM implementation (except for native targets that have none).
• Add a getOrCreatePrefix function that can be used to get an appropriate prefix for a given namespace. If there is no existing prefix, one will be created and added to the tag. If a prefixHint is given, this will be prioritised (to select from multiple prefixes)/to create a prefix if none is registered.
• Exceptions will now have the ability to provide more extensive location information. This includes adding file name information to the exception.
• The parser now partially parses internal DTD's and supports entities as per the standard. At this point external DTDs and entities are not supported (this is not a validating parser.). The work includes support of injecting entity parsing results into the parser (i.e. defining entities containing tags).

Incompatible API:

• There are a few incompatible changes in the DOM API. In particular: some return values have been made nullable (as they are defined as such explicitly by the DOM specification); NamedNodeList is made generic with Node as the base type (rather than Attr) - Note that for the attributes of an element, the generic type is still Attr; Some methods on platform only is

Changes:

• Move the native DOM implementation to the common module and make it available to all platforms (making it also available on nodejs). The implementation has also been extended to implement most DOM 3 features. Note that much of this is still experimental, and has partial tests.
• Note that the JavaScript implementation has some additional code that declares properties that match the native DOM api (it does not yet have isInstance compatibility)
• As a result of DOM work some signatures have been made nullable as that is required per the DOM specification (and semantics).
• Add new context element to Xml exception that should allow for more detailed context to be provided in exceptions. This generally covers element names. This helps in cases of attributes where the location information is insufficient (it is positioned at the start or end of the containing tag).
• Parsing of single characters now allows for xml Whitespace and will collapse the whitespace if there are more than 2 characters. It should be noted that to parse a single space character this must not be surrounded by whitespace (collapsing only applies if there are 2 or more characters and this would collapse to an empty string). The old behaviour only allowed a single character without surrounding whitespace.
• Standards compliant line ending handling. \n\r is not collapsed as a single line end anymore. Characters #x85 and [#2028](https://github.com/pdvrieze/xmlutil/issues/2028) are now handled as line end (unless preceded by \r)
• Update kotlinx.io support to 0.9.0, atomicfu to 0.31.0, kotlinx.serialization to 1.10.0, kotlinx.benchmark to 0.4.16, kotlin to 2.3.10, junit to 5.14.3.
• Always expand entities in attribute values (causing an exception if the entity

... (truncated)

Changelog

Sourced from io.github.pdvrieze.xmlutil:core's changelog.

1.0.0-rc3 The full DOM

(Jun 6, 2026) Features:

• There is now a common DOM implementation on all platforms that cooperates with the platform's DOM implementation (except for native targets that have none).
• Add a getOrCreatePrefix function that can be used to get an appropriate prefix for a given namespace. If there is no existing prefix, one will be created and added to the tag. If a prefixHint is given, this will be prioritised (to select from multiple prefixes)/to create a prefix if none is registered.
• Exceptions will now have the ability to provide more extensive location information. This includes adding file name information to the exception.
• The parser now partially parses internal DTD's and supports entities as per the standard. At this point external DTDs and entities are not supported (this is not a validating parser.). The work includes support of injecting entity parsing results into the parser (i.e. defining entities containing tags).

Incompatible API:

• There are a few incompatible changes in the DOM API. In particular: some return values have been made nullable (as they are defined as such explicitly by the DOM specification); NamedNodeList is made generic with Node as the base type (rather than Attr) - Note that for the attributes of an element, the generic type is still Attr; Some methods on platform only is

Changes:

• Move the native DOM implementation to the common module and make it available to all platforms (making it also available on nodejs). The implementation has also been extended to implement most DOM 3 features. Note that much of this is still experimental, and has partial tests.
• Note that the JavaScript implementation has some additional code that declares properties that match the native DOM api (it does not yet have isInstance compatibility)
• As a result of DOM work some signatures have been made nullable as that is required per the DOM specification (and semantics).
• Add new context element to xml exception that should allow for more detailed context to be provided in exceptions. This generally covers element names. This helps in cases of attributes where the location information is insufficient (it is positioned at the start or end of the containing tag).
• Parsing of single characters now allows for xml Whitespace and will collapse the whitespace if there are more than 2 characters. It should be noted that to parse a single space character this must not be surrounded by whitespace (collapsing only applies if there are 2 or more characters and this would collapse to an empty string). The old behaviour only allowed a single character without surrounding whitespace.
• Standards compliant line ending handling. \n\r is not collapsed as a single line end anymore. Characters #x85 and #2028 are now handled as line end (unless preceded by \r)
• Update kotlinx.io support to 0.9.0, atomicfu to 0.31.0, kotlinx.serialization to 1.10.0, kotlinx.benchmark to 0.4.16, kotlin to 2.3.10, junit to 5.14.3.

... (truncated)

Commits

• c02bf91 Prepare 1.0.0-rc3 release
• 0796b3c Merge branch 'dev'
• 53262ca Tidy the build configuration to fix binary validation errors (somehow renamin...
• c8b2e99 Use JavaScript prototype manipulation to add properties to add property gette...
• 0ffbba0 Move pages back to the pages branch
• 2fda2b1 Upgrade to Kotlin 2.4.0.
• f9dae4d Fix the JavaScript part of the code (for now). It still needs javascript hack...
• 4d97495 Make sure to store the updated error context upon adding context
• f89867b Record fixes in change log.
• cf777fc getPrefix should return null on a missing namespace (not "")
• Additional commits viewable in compare view

Updates io.github.pdvrieze.xmlutil:serialization from 1.0.0-rc2 to 1.0.0-rc3

Release notes

Sourced from io.github.pdvrieze.xmlutil:serialization's releases.

1.0.0-rc3 – The full DOM

Features:

• There is now a common DOM implementation on all platforms that cooperates with the platform's DOM implementation (except for native targets that have none).
• Add a getOrCreatePrefix function that can be used to get an appropriate prefix for a given namespace. If there is no existing prefix, one will be created and added to the tag. If a prefixHint is given, this will be prioritised (to select from multiple prefixes)/to create a prefix if none is registered.
• Exceptions will now have the ability to provide more extensive location information. This includes adding file name information to the exception.
• The parser now partially parses internal DTD's and supports entities as per the standard. At this point external DTDs and entities are not supported (this is not a validating parser.). The work includes support of injecting entity parsing results into the parser (i.e. defining entities containing tags).

Incompatible API:

• There are a few incompatible changes in the DOM API. In particular: some return values have been made nullable (as they are defined as such explicitly by the DOM specification); NamedNodeList is made generic with Node as the base type (rather than Attr) - Note that for the attributes of an element, the generic type is still Attr; Some methods on platform only is

Changes:

• Move the native DOM implementation to the common module and make it available to all platforms (making it also available on nodejs). The implementation has also been extended to implement most DOM 3 features. Note that much of this is still experimental, and has partial tests.
• Note that the JavaScript implementation has some additional code that declares properties that match the native DOM api (it does not yet have isInstance compatibility)
• As a result of DOM work some signatures have been made nullable as that is required per the DOM specification (and semantics).
• Add new context element to Xml exception that should allow for more detailed context to be provided in exceptions. This generally covers element names. This helps in cases of attributes where the location information is insufficient (it is positioned at the start or end of the containing tag).
• Parsing of single characters now allows for xml Whitespace and will collapse the whitespace if there are more than 2 characters. It should be noted that to parse a single space character this must not be surrounded by whitespace (collapsing only applies if there are 2 or more characters and this would collapse to an empty string). The old behaviour only allowed a single character without surrounding whitespace.
• Standards compliant line ending handling. \n\r is not collapsed as a single line end anymore. Characters #x85 and [#2028](https://github.com/pdvrieze/xmlutil/issues/2028) are now handled as line end (unless preceded by \r)
• Update kotlinx.io support to 0.9.0, atomicfu to 0.31.0, kotlinx.serialization to 1.10.0, kotlinx.benchmark to 0.4.16, kotlin to 2.3.10, junit to 5.14.3.
• Always expand entities in attribute values (causing an exception if the entity

... (truncated)

Changelog

Sourced from io.github.pdvrieze.xmlutil:serialization's changelog.

1.0.0-rc3 The full DOM

(Jun 6, 2026) Features:

• There is now a common DOM implementation on all platforms that cooperates with the platform's DOM implementation (except for native targets that have none).
• Add a getOrCreatePrefix function that can be used to get an appropriate prefix for a given namespace. If there is no existing prefix, one will be created and added to the tag. If a prefixHint is given, this will be prioritised (to select from multiple prefixes)/to create a prefix if none is registered.
• Exceptions will now have the ability to provide more extensive location information. This includes adding file name information to the exception.
• The parser now partially parses internal DTD's and supports entities as per the standard. At this point external DTDs and entities are not supported (this is not a validating parser.). The work includes support of injecting entity parsing results into the parser (i.e. defining entities containing tags).

Incompatible API:

• There are a few incompatible changes in the DOM API. In particular: some return values have been made nullable (as they are defined as such explicitly by the DOM specification); NamedNodeList is made generic with Node as the base type (rather than Attr) - Note that for the attributes of an element, the generic type is still Attr; Some methods on platform only is

Changes:

• Move the native DOM implementation to the common module and make it available to all platforms (making it also available on nodejs). The implementation has also been extended to implement most DOM 3 features. Note that much of this is still experimental, and has partial tests.
• Note that the JavaScript implementation has some additional code that declares properties that match the native DOM api (it does not yet have isInstance compatibility)
• As a result of DOM work some signatures have been made nullable as that is required per the DOM specification (and semantics).
• Add new context element to xml exception that should allow for more detailed context to be provided in exceptions. This generally covers element names. This helps in cases of attributes where the location information is insufficient (it is positioned at the start or end of the containing tag).
• Parsing of single characters now allows for xml Whitespace and will collapse the whitespace if there are more than 2 characters. It should be noted that to parse a single space character this must not be surrounded by whitespace (collapsing only applies if there are 2 or more characters and this would collapse to an empty string). The old behaviour only allowed a single character without surrounding whitespace.
• Standards compliant line ending handling. \n\r is not collapsed as a single line end anymore. Characters #x85 and #2028 are now handled as line end (unless preceded by \r)
• Update kotlinx.io support to 0.9.0, atomicfu to 0.31.0, kotlinx.serialization to 1.10.0, kotlinx.benchmark to 0.4.16, kotlin to 2.3.10, junit to 5.14.3.

... (truncated)

Commits

• c02bf91 Prepare 1.0.0-rc3 release
• 0796b3c Merge branch 'dev'
• 53262ca Tidy the build configuration to fix binary validation errors (somehow renamin...
• c8b2e99 Use JavaScript prototype manipulation to add properties to add property gette...
• 0ffbba0 Move pages back to the pages branch
• 2fda2b1 Upgrade to Kotlin 2.4.0.
• f9dae4d Fix the JavaScript part of the code (for now). It still needs javascript hack...
• 4d97495 Make sure to store the updated error context upon adding context
• f89867b Record fixes in change log.
• cf777fc getPrefix should return null on a missing namespace (not "")
• Additional commits viewable in compare view

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 show <dependency name> 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)