Bump @xmldom/xmldom from 0.7.5 to 0.7.8

[dependabot[bot]]

Bumps @xmldom/xmldom from 0.7.5 to 0.7.8.

Release notes

Sourced from @​xmldom/xmldom's releases.

0.7.8

Commits

Fixed

• fix: Restore ES5 compatibility [#452](https://github.com/xmldom/xmldom/issues/452) / [#453](https://github.com/xmldom/xmldom/issues/453)

Thank you, @​fengxinming, for your contributions

0.7.7

Commits

Fixed

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

Thank you, @​frumioj, @​cjbarth, @​markgollnick for your contributions

0.7.6

Commits

Fixed

• Avoid iterating over prototype properties [#441](https://github.com/xmldom/xmldom/issues/441) / [#437](https://github.com/xmldom/xmldom/issues/437) / [#436](https://github.com/xmldom/xmldom/issues/436)

Thank you, @​jftanner, @​Supraja9726 for your contributions

Changelog

Sourced from @​xmldom/xmldom's changelog.

0.7.8

Fixed

• fix: Restore ES5 compatibility [#452](https://github.com/xmldom/xmldom/issues/452) / [#453](https://github.com/xmldom/xmldom/issues/453)

Thank you, @​fengxinming, for your contributions

0.9.0-beta.4

Fixed

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

Chore

• update multiple devDependencies
• Add eslint-plugin-node for lib [#448](https://github.com/xmldom/xmldom/issues/448) / [#190](https://github.com/xmldom/xmldom/issues/190)
• style: Apply prettier to all code [#447](https://github.com/xmldom/xmldom/issues/447) / [#29](https://github.com/xmldom/xmldom/issues/29) / [#130](https://github.com/xmldom/xmldom/issues/130)

Thank you, @​XhmikosR, @​awwright, @​frumioj, @​cjbarth, @​markgollnick for your contributions

0.8.4

Fixed

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

Thank you, @​frumioj, @​cjbarth, @​markgollnick for your contributions

0.7.7

Fixed

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

... (truncated)

Commits

• 0d6e3a1 0.7.8
• 74e25a6 fix: Restore ES5 compatibility (#452)
• fe5b043 0.7.7
• 8a3173d docs: Prepare CHANGELOG for 0.7.7
• c02f786 Merge pull request from GHSA-crh6-fp67-6883
• 3ca016d 0.7.6
• b28e631 docs: Prepare CHANGELOG for 0.7.6
• 1f20aee fix: Backport PR-437 to 0.7.x branch
• See full diff 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 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/FixMyBerlin/fixmy.frontend/network/alerts).

[codecov[bot]]

Codecov Report

Base: 34.60% // Head: 34.60% // No change to project coverage :thumbsup:

Coverage data is based on head (6ce12dd) compared to base (7a9b210). Patch has no changes to coverable lines.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #1087 +/- ## ======================================== Coverage 34.60% 34.60% ======================================== Files 527 527 Lines 9454 9454 Branches 2029 2029 ======================================== Hits 3272 3272 Misses 5735 5735 Partials 447 447 ``` | Flag | Coverage Δ | | |---|---|---| | unittests | `34.60% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=FixMyBerlin#carryforward-flags-in-the-pull-request-comment) to find out more. Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=FixMyBerlin). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=FixMyBerlin)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.