Skip to content

R11DT-3616 - Update lodash to version 4.17.23 - #202

Merged
OS-miguelfreitas merged 1 commit into
b11from
R11DT-3616-lodash-vul-v2
Jan 28, 2026
Merged

OS-miguelfreitas merged 1 commit into
b11from
R11DT-3616-lodash-vul-v2

Conversation

@OS-alexandretome

Copy link
Copy Markdown

…n; modify swagger-ui bundle files for compatibility and add missing newlines.

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

…n; modify swagger-ui bundle files for compatibility and add missing newlines.
@OS-miguelfreitas
OS-miguelfreitas merged commit 81cd479 into b11 Jan 28, 2026
9 checks passed
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.

2 participants