Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency @xmldom/xmldom to ^0.8.0 #7

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 2, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@xmldom/xmldom ^0.7.5 -> ^0.8.0 age adoption passing confidence

Warning

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


Release Notes

xmldom/xmldom (@​xmldom/xmldom)

v0.8.10

Compare Source

Fixed
  • dom: prevent iteration over deleted items #514/ #499

Thank you, @​qtow, for your contributions

v0.8.9

Compare Source

Fixed
  • Set nodeName property in ProcessingInstruction #509 / #505

Thank you, @​cjbarth, for your contributions

v0.8.8

Compare Source

Fixed
  • extend list of HTML entities #489

Thank you, @​zorkow, for your contributions

v0.8.7

Compare Source

Fixed
  • properly parse closing where the last attribute has no value #485 / #486

Thank you, @​bulandent, for your contributions

v0.8.6

Compare Source

Fixed
  • Properly check nodes before replacement #457 / #455 / #456

Thank you, @​edemaine, @​pedro-l9, for your contributions

v0.8.5

Compare Source

Fixed
  • fix: Restore ES5 compatibility #452 / #453

Thank you, @​fengxinming, for your contributions

v0.8.4

Compare Source

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

v0.8.3

Compare Source

Fixed
  • Avoid iterating over prototype properties #437 / #436

Thank you, @​Supraja9726 for your contributions

v0.8.2

Compare Source

Fixed
  • fix(dom): Serialize &gt; as specified (#​395) #58
Other
  • docs: Add nodeType values to public interface description #396
  • test: Add executable examples for node and typescript #317
  • fix(dom): Serialize &gt; as specified #395
  • chore: Add minimal Object.assign ponyfill #379
  • docs: Refine release documentation #378
  • chore: update various dev dependencies

Thank you @​niklasl, @​cburatto, @​SheetJSDev, @​pyrsmk for your contributions

v0.8.1

Compare Source

Fixed
  • dom: prevent iteration over deleted items #514/ #499

Thank you, @​qtow, for your contributions

v0.8.0

Compare Source

Fixed
  • Normalize all line endings according to XML specs 1.0 and 1.1
    BREAKING CHANGE: Certain combination of line break characters are normalized to a single \n before parsing takes place and will no longer be preserved.
  • XMLSerializer: Preserve whitespace character references #284 / #310
    BREAKING CHANGE: If you relied on the not spec compliant preservation of literal \t, \n or \r in attribute values.
    To preserve those you will have to create XML that instead contains the correct numerical (or hexadecimal) equivalent (e.g. &#x9;, &#xA;, &#xD;).
  • Drop deprecated exports DOMImplementation and XMLSerializer from lib/dom-parser.js #​53 / #309
    BREAKING CHANGE: Use the one provided by the main package export.
  • dom: Remove all links as part of removeChild #343 / #355
Chore
  • ci: Restore latest tested node version to 16.x #325
  • ci: Split test and lint steps into jobs #111 / #304
  • Pinned and updated devDependencies

Thank you @​marrus-sh, @​victorandree, @​mdierolf, @​tsabbay, @​fatihpense for your contributions


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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/xmldom-xmldom-0.x branch from ed5a410 to c8c14f3 Compare March 2, 2024 13:40
@volschin volschin merged commit 2fd8302 into main Mar 2, 2024
1 check passed
@volschin volschin deleted the renovate/xmldom-xmldom-0.x branch March 2, 2024 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant