Skip to content

Conversation

Picnic-DevPla-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
sonar-maven-plugin (source) build minor 5.0.0.4389 -> 5.1.0.4751

Release Notes

SonarSource/sonar-scanner-maven (sonar-maven-plugin)

v5.1.0.4751

Compare Source

Release notes - Sonar Scanner for Maven - 5.1

New Feature

SCANMAVEN-264 Add support for SonarQube Cloud regions

Bug

SCANMAVEN-228 Irrelevant encrypted properties should not be passed to the scanner engine

Task

SCANMAVEN-242 Migrate from single module to a multi-module structure

SCANMAVEN-250 Fix broken links coming from the relocation-pom's parent

SCANMAVEN-254 Update parent pom to version 81.0.0.2300

SCANMAVEN-257 Update headers for 2025

SCANMAVEN-258 Conditionally run tests using sonar.password in ITs

SCANMAVEN-260 Update CODEOWNERS after reorg

SCANMAVEN-261 Validate IT using the latest maven 4 release candidate 2

SCANMAVEN-262 Fix quality flaws: remove unnecessary public modifiers

SCANMAVEN-265 Upgrade sonar-scanner-java-library to latest version

SCANMAVEN-266 Analyze integration tests

SCANMAVEN-269 Prepare next development iteration 5.1

SCANMAVEN-271 Fix readability issues in ProxyTest

SCANMAVEN-272 Increase memory because maven 4.0.0-rc-2 fails with out of memory exception

SCANMAVEN-274 Fix quality flaws

SCANMAVEN-277 remove unused third-party-licenses.sh

SCANMAVEN-278 Fix quality flaws

SCANMAVEN-279 Clean up tech debt in Maven Scanner

SCANMAVEN-282 Update plexus-sec-dispatcher to fix CVE-2017-1000487

SCANMAVEN-284 Migrate releasability check to v2, fix property-dump-plugin to be excluded by releasability check (not released)

Improvement

SCANMAVEN-256 Remove (now redundant) server type logging

SCANMAVEN-276 ScannerEngineBootstrapper.isSuccessful() should be verified before calling getEngineFacade()

SCANMAVEN-280 Log the SonarQube Cloud Region


  • If you want to rebase/retry this PR, check this box

@Picnic-DevPla-Bot
Copy link
Contributor Author

Picnic-DevPla-Bot commented Mar 26, 2025

Suggested commit message:

Upgrade sonar-maven-plugin 5.0.0.4389 -> 5.1.0.4751 (#1614)

See:
- https://github.com/SonarSource/sonar-scanner-maven/releases/tag/5.1.0.4751
- https://github.com/SonarSource/sonar-scanner-maven/compare/5.0.0.4389...5.1.0.4751

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Stephan202 Stephan202 added this to the 0.22.0 milestone Mar 26, 2025
Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated suggested commit message.

@Picnic-DevPla-Bot Picnic-DevPla-Bot force-pushed the renovate/sonar-maven-plugin-5.x branch from 02df149 to 69d1c75 Compare March 28, 2025 02:03
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

1 similar comment
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Picnic-DevPla-Bot Picnic-DevPla-Bot force-pushed the renovate/sonar-maven-plugin-5.x branch from 69d1c75 to 8de83b7 Compare April 1, 2025 01:14
@Picnic-DevPla-Bot Picnic-DevPla-Bot force-pushed the renovate/sonar-maven-plugin-5.x branch from 8de83b7 to 7a3098a Compare April 2, 2025 01:20
Copy link

github-actions bot commented Apr 2, 2025

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link

sonarqubecloud bot commented Apr 2, 2025

@rickie rickie merged commit 5d8d271 into master Apr 2, 2025
17 checks passed
@rickie rickie deleted the renovate/sonar-maven-plugin-5.x branch April 2, 2025 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants