Bump fast-xml-parser from 5.5.9 to 5.7.1 #1524
1/3 Fail(s): MILESTONE
Status: FAIL
Here are some stats of the run:
3 validations were ran.
2 PASSED
1 FAILED
Details
❌ Validator: MILESTONE
- ❌ A milestone must be assigned to this pull request
Input :
Settings :{"no_empty":{"enabled":true,"message":"A milestone must be assigned to this pull request"}}
✔️ Validator: LABEL
- ✔️ The label is not empty
Input : dependencies,javascript
Settings :{"no_empty":{"enabled":true,"message":"A label must be assigned to this pull request"}}
✔️ Validator: DESCRIPTION
- ✔️ The description is not empty
Input : Bumps fast-xml-parser from 5.5.9 to 5.7.1.
Release notes
Sourced from fast-xml-parser's releases.
upgrade
@nodable/entitiesand FXB
- Use
@nodable/entitiesv2.1.0
- breaking changes
- single entity scan. You're not allowed to use entity value to form another entity name.
- you cant add numeric external entity
- entity error message when expantion limit is crossed might change
- typings are updated for new options related to process entity
- please follow documentation of
@nodable/entitiesfor more detail.- performance
- if processEntities is false, then there should not be impact on performance.
- if processEntities is true, but you dont pass entity decoder separately then performance may degrade by approx 8-10%
- if processEntities is true, and you pass entity decoder separately
- if no entity then performance should be same as before
- if there are entities then performance should be increased from past versions
- ignoreAttributes is not required to be set to set xml version for NCR entity value
- update 'fast-xml-builder' to sanitize malicious CDATA and comment's content
use
@nodable/entitiesto replace entities
- No API change
- No change in performance for basic usage
- No typing change
- No config change
- new dependency
- breaking: error messages for entities might have been changed.
Full Changelog: NaturalIntelligence/fast-xml-parser@v5.5.12...v5.6.0
performance improvment, increase entity expansion default limit
- increase default entity explansion limit as many projects demand for that
maxEntitySize: 10000, maxExpansionDepth: 10000, maxTotalExpansions: Infinity, maxExpandedLength: 100000, maxEntityCount: 1000,
- performance improvement
- reduce calls to toString
- early return when entities are not present
- prepare rawAttrsForMatcher only if user sets
jPath: falseFull Changelog: NaturalIntelligence/fast-xml-parser@v5.5.9...v5.5.10
Changelog
Sourced from fast-xml-parser's changelog.
Note: If you find missing information about particular minor version, that version must have been changed without any functional change in this library.
Note: Due to some last quick changes on v4, detail of v4.5.3 & v4.5.4 are not updated here. v4.5.4x is the last tag of v4 in github repository. I'm extremely sorry for the confusion
5.7.1 / 2026-04-20
- fix #705: attributesGroupName working with preserveOrder
- fix #817: stackoverflow when tag expression is very long
5.7.0 / 2026-04-17
- Use
@nodable/entitiesv2.1.0
- breaking changes
- single entity scan. You're not allowed to user entity value to form another entity name.
- you cant add numeric external entity
- entity error message when expantion limit is crossed might change
- typings are updated for new options related to process entity
- please follow documentation of
@nodable/entitiesfor more detail.- performance
- if processEntities is false, then there should not be impact on performance.
- if processEntities is true, but you dont pass entity decoder separately then performance may degrade by approx 8-10%
- if processEntities is true, and you pass entity decoder separately
- if no entity then performance should be same as before
- if there are entities then performance should be increased from past versions
- ignoreAttributes is not required to be set to set xml version for NCR entity value
- update 'fast-xml-builder' to sanitize malicious CDATA and comment's content
5.6.0 / 2026-04-15
- fix: entity replacement for numeric entities
- use
@nodable/entitiesto replace entities
- this may change some error messages related to entities expansion limit or inavlid use
- post check would be exposed in future version
5.5.12 / 2026-04-13
- Performance Improvement: update path-expression-matcher
- use proxy pattern than Proxy class
5.5.11 / 2026-04-08
- Performance Improvement
- integrate ExpressionSet for stopNodes
5.5.10 / 2026-04-03
- increase default entity explansion limit as many projects demand for that
- performance improvement
- reduce calls to toString
- early return when entities are not present
- prepare rawAttrsForMatcher only if user sets
jPath: false5.5.9 / 2026-03-23
- combine typing files
... (truncated)
Commits
0f08303fix typof529642update to release v5.7.052a8583Revert "improve performance of attributes reading"8d187f9update buildere174168improve performance of attributes reading79a8ddeupdate docsf5cd5a5set xml version to decoder even if attributes are ignoredf44b923remove unwanted tests869ec8bUse@nodable/entitiesv2.1.07cb49e5update release detail- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.