[CSR-0] chore: Bump xmlbuilder2 from 3.1.1 to 4.0.3 - #384
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [xmlbuilder2](https://github.com/oozcitak/xmlbuilder2) from 3.1.1 to 4.0.3. - [Changelog](https://github.com/oozcitak/xmlbuilder2/blob/master/CHANGELOG.md) - [Commits](oozcitak/xmlbuilder2@v3.1.1...v4.0.3) --- updated-dependencies: - dependency-name: xmlbuilder2 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
AssigneesThe following users could not be added as assignees: Please fix the above issues or remove invalid values from |
Contributor
|
Superseded by #393, which applies this same bump together with the other mergeable Dependabot updates in a single lockfile-consistent change (verified: Closing in favour of that PR. |
agoldis
added a commit
that referenced
this pull request
Jul 30, 2026
Consolidates the mergeable Dependabot PRs into a single lockfile-consistent change, and resolves GHSA-mh99-v99m-4gvg (CVE-2026-14257). Dependency updates (supersedes #384, #385, #386, #387): - xmlbuilder2 3.1.1 -> 4.0.3 - @release-it/conventional-changelog 10.0.1 -> 12.0.0 (all packages) - @babel/preset-env 7.26.9 -> 8.0.2 (examples/jest) - @typescript-eslint/parser 8.0.0 -> 8.65.0 Security fix: brace-expansion had 9 nested copies still on vulnerable 1.1.16/2.1.2 even after the top-level bump in #382, which is why the alert stayed open. Each major line has its own backport, so per-major overrides patch every copy without forcing a breaking jest-config major. Verified: xmlbuilder2 3.x and 4.x produce byte-identical JUnit XML for this codebase's usage (unicode, XML escaping, CDATA, "]]>" sequences). The advisory PoC ('{a,b}'.repeat(1500)), which crashed the process with an uncatchable OOM, now returns bounded output on all three major lines. Excludes @babel/code-frame 8.0.0 (#383, #389): v8 changed `column` from 1-based to 0-based. error.ts parses columns from V8 stack traces, which are 1-based, so the bump shifts every code-frame caret one column right. Needs a compensating fix, so it is left for a separate change. Co-authored-by: Andrew Goldis <agoldis@gmail.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Contributor
Author
|
Looks like xmlbuilder2 is up-to-date now, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps xmlbuilder2 from 3.1.1 to 4.0.3.
Changelog
Sourced from xmlbuilder2's changelog.
Commits
5ca638bMerge branch 'mdovhopo-master'8d50e14Bump version5c122b3Merge branch 'master' into mdovhopo-master9617fcfUpdate changelogd3b76faMerge branch 'master' into mdovhopo-masterf7bacc3Wait no it's actually cjs2d6c7e3Declare that the package is an ES Module6f83432remove browser source configuration, as webpack seems to be disabled460b5c4Add sponsorship links6c2a110Update fundingDependabot 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)