Bump xml from 0.91.3 to 1.0.0

[dependabot]

Bumps xml from 0.91.3 to 1.0.0.
Updates io.github.pdvrieze.xmlutil:serialization from 0.91.3 to 1.0.0

Release notes

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

1.0.0 – To infinity, and beyond

Fixes:

• Remove usages of removeLast() to avoid issues on Android below API-level 35. Fixes #367.
• Fix Attr in the common DOM implementation not having its owner set/tracked appropriately.
• Ensure that the module structure matches the old structure from 1.0.0-rc2 and before.

Changes:

• The core-compat module is no longer published. Use core/core-jvm, and if integration with the native parser is needed, add the core-jdk or core-android modules.

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

... (truncated)

Changelog

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

1.0.0 To infinity and beyond

(Jun 28, 2026) Fixes:

• Remove usages of removeLast() to avoid issues on Android below API-level 35. Fixes #367.
• Fix Attr in the common DOM implementation not having its owner set/tracked appropriately.
• Ensure that the module structure matches the old structure from 1.0.0-rc2 and before.

Changes:

• The core-compat module is no longer published. Use core/core-jvm, and if integration with the native parser is needed, add the core-jdk or core-android modules.

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

... (truncated)

Commits

• 0321996 Prepare 1.0.0 release
• 540de5e Merge branch 'dev'
• f504f79 Repurpose the compat module to generate a core-jvmcommon component that is ju...
• fdce51f Update gradle wrapper to 9.6.1 and amend build files to remove deprecated pat...
• 47ff8a5 Remove compat as no longer needed
• 8b811c9 Update changelog to note the fix in attribute owners
• 36fd38d Put testutil back into the xmlutil group
• 7863b88 Fix setting/updating owner element to attributes.
• 1b0a47b Group test support for the XS test suite.
• b2f6169 Tidy the test suite.
• Additional commits viewable in compare view

Updates io.github.pdvrieze.xmlutil:core-jdk from 0.91.3 to 1.0.0

Release notes

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

1.0.0 – To infinity, and beyond

Fixes:

• Remove usages of removeLast() to avoid issues on Android below API-level 35. Fixes #367.
• Fix Attr in the common DOM implementation not having its owner set/tracked appropriately.
• Ensure that the module structure matches the old structure from 1.0.0-rc2 and before.

Changes:

• The core-compat module is no longer published. Use core/core-jvm, and if integration with the native parser is needed, add the core-jdk or core-android modules.

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

... (truncated)

Changelog

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

1.0.0 To infinity and beyond

(Jun 28, 2026) Fixes:

• Remove usages of removeLast() to avoid issues on Android below API-level 35. Fixes #367.
• Fix Attr in the common DOM implementation not having its owner set/tracked appropriately.
• Ensure that the module structure matches the old structure from 1.0.0-rc2 and before.

Changes:

• The core-compat module is no longer published. Use core/core-jvm, and if integration with the native parser is needed, add the core-jdk or core-android modules.

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

... (truncated)

Commits

• 0321996 Prepare 1.0.0 release
• 540de5e Merge branch 'dev'
• f504f79 Repurpose the compat module to generate a core-jvmcommon component that is ju...
• fdce51f Update gradle wrapper to 9.6.1 and amend build files to remove deprecated pat...
• 47ff8a5 Remove compat as no longer needed
• 8b811c9 Update changelog to note the fix in attribute owners
• 36fd38d Put testutil back into the xmlutil group
• 7863b88 Fix setting/updating owner element to attributes.
• 1b0a47b Group test support for the XS test suite.
• b2f6169 Tidy the test suite.
• Additional commits viewable in compare view