Fix fast-xml-parser vulnerability by bumping aws dependencies#390
Merged
Fix fast-xml-parser vulnerability by bumping aws dependencies#390
Conversation
liamness
added
the
maintenance
liamness
force-pushed
the
ld/fix-fast-xml-parser-vulnerability
branch
2 times, most recently
from
1861da3 to
c7745af
Compare
liamness
force-pushed
the
ld/fix-fast-xml-parser-vulnerability
branch
from
c7745af to
da4ac8e
Compare
dblatcher
approved these changes
Feb 18, 2026
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
3 participants
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.
What does this change?
Responding to dependabot alert: https://github.com/guardian/pinboard/security/dependabot/188
This bumps all of the following to
3.990.0How has this change been tested?
Going to deploy to CODE and do a general smoke test. Think the trickiest thing to check will be email notifications?
Have deployed and all seems well in composer. Also checked email notifications, which seem to work just fine too:
How can we measure success?
Have we considered potential risks?
Images
Accessibility