Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(log4j): update log4j version #8241

Merged
merged 5 commits into from
Apr 6, 2024
Merged

fix(log4j): update log4j version #8241

merged 5 commits into from
Apr 6, 2024

Conversation

moabu
Copy link
Member

@moabu moabu commented Apr 5, 2024

Prepare


Description

Target issue

closes #8240

Implementation Details


Test and Document the changes

  • Static code analysis has been run locally and issues have been fixed
  • Relevant unit and integration tests have been added/updated
  • Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
Copy link

sonarcloud bot commented Apr 5, 2024

Quality Gate Passed Quality Gate passed for 'jans-config-api-parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@yurem yurem enabled auto-merge (squash) April 5, 2024 15:53
@moabu moabu disabled auto-merge April 6, 2024 00:59
@moabu moabu merged commit 4b4da3b into main Apr 6, 2024
4 checks passed
@moabu moabu deleted the fix-log4j-version branch April 6, 2024 01:01
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.

fix: possible memery leak from log4j version
9 participants