Update lockfiles to remediate fast-xml-builder Dependabot alerts#214
Merged
Merged
Conversation
Agent-Logs-Url: https://github.com/CodeWithAsheville/zipcase/sessions/af1514f0-0e74-4b5f-9423-e7fdaa8b3ced Co-authored-by: jayhill <116148+jayhill@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
jayhill
May 9, 2026 16:13
View session
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.
The open Dependabot alerts were caused by transitive resolutions of
fast-xml-builderat1.1.4, which is within the vulnerable range. This updates the affected lockfiles so installs resolve a patched release without changing top-level package manifests.Scope
frontend/package-lock.jsonserverless/package-lock.jsonDependency resolution
fast-xml-builderresolution from1.1.4to1.2.0path-expression-matcher→1.5.0xml-naming→0.1.0Impact
fast-xml-builderalert path while keeping the change limited to dependency resolution data already captured in lockfiles