August 2026 - notifications

[xwiki/xwiki-platform] 5cc73c: [Misc] Take the deliberate bug out of the legacy m...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/sonar-pr-selftest Home: https://github.com/xwiki/xwiki-platform Commit: 5cc73c61bcc461ca4893b9f5ce3be86a6197367a https://github.com/xwiki/xwiki-platform/commit/5cc73c61bcc461ca4893b9f5ce3b… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-annotation/src/main/java/org/xwiki/annotation/internal/AnnotationVelocityContextInitializer.java Log Message: ----------- [Misc] Take the deliberate bug out of the legacy module * Remove the java:S1764 bug now that the quality gate has been seen to fail on it, keeping a comment in the legacy module so that it stays among the modules the analysis selects: the run is then expected to go green on a legacy module rather than by leaving it out. This pull request is not meant to be merged and its changes have to be reverted. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications

1 0

[xwiki/xwiki-platform] 3f635a: [Misc] Check the SonarCloud pull request analysis ...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/sonar-pr-selftest Home: https://github.com/xwiki/xwiki-platform Commit: 3f635a862175ed497269c33e563b04e11538ccdc https://github.com/xwiki/xwiki-platform/commit/3f635a862175ed497269c33e563b… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M xwiki-platform-core/pom.xml M xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-annotation/src/main/java/org/xwiki/annotation/internal/AnnotationVelocityContextInitializer.java Log Message: ----------- [Misc] Check the SonarCloud pull request analysis on an aggregator pom and on a legacy module * Change an aggregator pom and a legacy module, the two paths the reworked module selection has no run behind it for, so that the analysis is exercised on a real pull request. * Introduce a bug SonarQube reports, java:S1764, in the legacy module: the quality gate is expected to fail on it, a pull request adding an issue to a legacy module having passed it until now. This pull request is not meant to be merged and its changes have to be reverted. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications

1 0

[xwiki/xwiki-rendering] 7c866c: [Misc] Analyze a changed pom with its own module i...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-rendering Commit: 7c866c591119209e2855eb489552525ac94a2b41 https://github.com/xwiki/xwiki-rendering/commit/7c866c591119209e2855eb48955… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/workflows/sonar-pr.yml Log Message: ----------- [Misc] Analyze a changed pom with its own module instead of the whole reactor * Select the module holding a changed pom.xml along with its ancestors, the root pom and an aggregator included, instead of widening to the whole reactor. Every condition of the quality gate is on a new code metric, and the new code a pom change brings is that pom's own lines, which are analyzed with the module holding them: a module the pull request does not change owns no new line, so building the subtree an aggregator drives produces nothing the gate can read. * A change to the root pom or to one of the 150 aggregators of the xwiki-platform reactor used to rebuild and rescan its 577 modules. Replayed over the last 300 commits of that repository the selection now leaves no whole reactor build at all, that staying the fallback for what cannot be decided: a base branch missing from the clone, a pom that cannot be read, a module declared by a profile Maven activates on its own. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-rendering/settings/notifications

1 0

[xwiki/xwiki-commons] ef007e: [Misc] Analyze a changed pom with its own module i...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-commons Commit: ef007e02f03f3b6a400ffa94d8ffbee22d6915ea https://github.com/xwiki/xwiki-commons/commit/ef007e02f03f3b6a400ffa94d8ffb… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/workflows/sonar-pr.yml Log Message: ----------- [Misc] Analyze a changed pom with its own module instead of the whole reactor * Select the module holding a changed pom.xml along with its ancestors, the root pom and an aggregator included, instead of widening to the whole reactor. Every condition of the quality gate is on a new code metric, and the new code a pom change brings is that pom's own lines, which are analyzed with the module holding them: a module the pull request does not change owns no new line, so building the subtree an aggregator drives produces nothing the gate can read. * A change to the root pom or to one of the 150 aggregators of the xwiki-platform reactor used to rebuild and rescan its 577 modules. Replayed over the last 300 commits of that repository the selection now leaves no whole reactor build at all, that staying the fallback for what cannot be decided: a base branch missing from the clone, a pom that cannot be read, a module declared by a profile Maven activates on its own. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-commons/settings/notifications

1 0

[xwiki/xwiki-platform] 72c99e: [Misc] Analyze a changed pom with its own module i...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-platform Commit: 72c99e4771b1f2a98dc1da837d9552309cd0154e https://github.com/xwiki/xwiki-platform/commit/72c99e4771b1f2a98dc1da837d95… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/workflows/sonar-pr.yml Log Message: ----------- [Misc] Analyze a changed pom with its own module instead of the whole reactor * Select the module holding a changed pom.xml along with its ancestors, the root pom and an aggregator included, instead of widening to the whole reactor. Every condition of the quality gate is on a new code metric, and the new code a pom change brings is that pom's own lines, which are analyzed with the module holding them: a module the pull request does not change owns no new line, so building the subtree an aggregator drives produces nothing the gate can read. * A change to the root pom or to one of the 150 aggregators of the xwiki-platform reactor used to rebuild and rescan its 577 modules. Replayed over the last 300 commits of that repository the selection now leaves no whole reactor build at all, that staying the fallback for what cannot be decided: a base branch missing from the clone, a pom that cannot be read, a module declared by a profile Maven activates on its own. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications

1 0

[xwiki/xwiki-docker] 56610b: [Misc] Track the database images on their "latest"...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-docker Commit: 56610b6fba4999f040c486c2d0c0e793c80b4c69 https://github.com/xwiki/xwiki-docker/commit/56610b6fba4999f040c486c2d0c0e7… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/renovate.json5 M 16/mariadb-tomcat/docker-compose.yml M 16/mysql-tomcat/docker-compose.yml M 16/postgres-tomcat/docker-compose.yml M 17/mariadb-tomcat/docker-compose.yml M 17/mysql-tomcat/docker-compose.yml M 17/postgres-tomcat/docker-compose.yml M 18.4/mariadb-tomcat/docker-compose.yml M 18.4/mysql-tomcat/docker-compose.yml M 18.4/postgres-tomcat/docker-compose.yml M 18/mariadb-tomcat/docker-compose.yml M 18/mysql-tomcat/docker-compose.yml M 18/postgres-tomcat/docker-compose.yml M template/docker-compose.yml Log Message: ----------- [Misc] Track the database images on their "latest" tag * Track the mysql, mariadb and postgres images of the generated docker-compose.yml on their "latest" tag rather than on a pinned major. That is the tag XWiki's own CI validates as the supported database configuration, and it removes the pin that had to be bumped at every database release. * Stop Renovate from proposing updates against the generated docker-compose.yml files, which the Gradlew Check action rejects and the next './gradlew' run reverts. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-docker/settings/notifications

1 0

[xwiki/xwiki-rendering] 3627a3: [Misc] Cover the legacy modules in the SonarCloud ...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-rendering Commit: 3627a307a059cacafa6a286fbe96ca0ab39af11b https://github.com/xwiki/xwiki-rendering/commit/3627a307a059cacafa6a286fbe9… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/workflows/sonar-pr.yml Log Message: ----------- [Misc] Cover the legacy modules in the SonarCloud pull request analysis * Activate the legacy profile, so that the -legacy modules are part of the reactor this job builds. The master analysis covers them, ci.xwiki.org running its quality build with that profile, so a pull request adding an issue to one of them used to pass the gate and turn master red afterwards. * Derive the modules to select from the reactor Maven itself builds, reading the poms as XML and for the profiles the build activates, rather than scanning their text: a pom holds <profiles> and <module> elements inside comments, which the text scan took for real ones, and a module declared as a nested or a relative path was not resolved at all. * Stop widening to the whole reactor when the changed aggregator pom belongs to no module of that reactor, such as the pom of a functional test module, of a distribution module or of a project a module ships under src/it. Such a pom drives nothing this job analyzes. * Read the changed paths with git diff -z, so that a path git would otherwise quote, and which no walk up the directories then resolves, is not dropped without a word. * Widen to the whole reactor when a changed file belongs to a module declared by a profile Maven activates on its own, since whether the reactor holds it is exactly what cannot be decided here. * Take the profiles from a single job level variable, so that the reactor the selection reasons about cannot drift from the reactor the build and the analysis use. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-rendering/settings/notifications

1 0

[xwiki/xwiki-commons] ec91cc: [Misc] Cover the legacy modules in the SonarCloud ...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-commons Commit: ec91cc55badefe54afc25b6480755d40b9cc8fc3 https://github.com/xwiki/xwiki-commons/commit/ec91cc55badefe54afc25b6480755… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/workflows/sonar-pr.yml Log Message: ----------- [Misc] Cover the legacy modules in the SonarCloud pull request analysis * Activate the legacy profile, so that the -legacy modules are part of the reactor this job builds. The master analysis covers them, ci.xwiki.org running its quality build with that profile, so a pull request adding an issue to one of them used to pass the gate and turn master red afterwards. * Derive the modules to select from the reactor Maven itself builds, reading the poms as XML and for the profiles the build activates, rather than scanning their text: a pom holds <profiles> and <module> elements inside comments, which the text scan took for real ones, and a module declared as a nested or a relative path was not resolved at all. * Stop widening to the whole reactor when the changed aggregator pom belongs to no module of that reactor, such as the pom of a functional test module, of a distribution module or of a project a module ships under src/it. Such a pom drives nothing this job analyzes. * Read the changed paths with git diff -z, so that a path git would otherwise quote, and which no walk up the directories then resolves, is not dropped without a word. * Widen to the whole reactor when a changed file belongs to a module declared by a profile Maven activates on its own, since whether the reactor holds it is exactly what cannot be decided here. * Take the profiles from a single job level variable, so that the reactor the selection reasons about cannot drift from the reactor the build and the analysis use. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-commons/settings/notifications

1 0

[xwiki/xwiki-platform] 46f200: [Misc] Cover the legacy modules in the SonarCloud ...
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-platform Commit: 46f2001d33e7c625aab87487506bdfa9db4d53ee https://github.com/xwiki/xwiki-platform/commit/46f2001d33e7c625aab87487506b… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-08-27 (Thu, 27 Aug 2026) Changed paths: M .github/workflows/sonar-pr.yml Log Message: ----------- [Misc] Cover the legacy modules in the SonarCloud pull request analysis * Activate the legacy profile, so that the -legacy modules are part of the reactor this job builds. The master analysis covers them, ci.xwiki.org running its quality build with that profile, so a pull request adding an issue to one of them used to pass the gate and turn master red afterwards. * Derive the modules to select from the reactor Maven itself builds, reading the poms as XML and for the profiles the build activates, rather than scanning their text: a pom holds <profiles> and <module> elements inside comments, which the text scan took for real ones, and a module declared as a nested or a relative path was not resolved at all. * Stop widening to the whole reactor when the changed aggregator pom belongs to no module of that reactor, such as the pom of a functional test module, of a distribution module or of a project a module ships under src/it. Such a pom drives nothing this job analyzes. * Read the changed paths with git diff -z, so that a path git would otherwise quote, and which no walk up the directories then resolves, is not dropped without a word. * Widen to the whole reactor when a changed file belongs to a module declared by a profile Maven activates on its own, since whether the reactor holds it is exactly what cannot be decided here. * Take the profiles from a single job level variable, so that the reactor the selection reasons about cannot drift from the reactor the build and the analysis use. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications

1 0

[xwiki/xwiki-platform]
by XWiki Notifications 27 Aug '26

27 Aug '26

Branch: refs/heads/sonar-pr-align Home: https://github.com/xwiki/xwiki-platform To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications

1 0