Branch: refs/heads/stable-17.4.x
Home: https://github.com/xwiki/xwiki-platform
Commit: f9258878894bb91cd7df9354e40bc23c8e7e8e15
https://github.com/xwiki/xwiki-platform/commit/f9258878894bb91cd7df9354e40b…
Author: Thomas Mortagne <thomas.mortagne(a)gmail.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M xwiki-platform-core/xwiki-platform-annotation/xwiki-platform-annotation-io/src/main/java/org/xwiki/annotation/io/internal/DefaultIOService.java
Log Message:
-----------
XWIKI-23353: Abusive modification of the cached document when deleting an annotation from the annotation box
(cherry picked from commit 58d40112a527b8fb621cb716ec918a9b14c355f3)
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications
Branch: refs/heads/master
Home: https://github.com/xwiki-contrib/book-versions
Commit: ae4fdf83321cd39358c305f196b8642e8159cd8b
https://github.com/xwiki-contrib/book-versions/commit/ae4fdf83321cd39358c30…
Author: Raluca Stavro <rstavro(a)xwiki.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M application-book-versions-api/pom.xml
M application-book-versions-common-ui/pom.xml
M application-book-versions-default/pom.xml
M application-book-versions-publish-ui/pom.xml
M application-book-versions-ui/pom.xml
M application-book-versions-xip/pom.xml
M pom.xml
Log Message:
-----------
[maven-release-plugin] prepare for next development iteration
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/book-versions/settings/notifications
Branch: refs/heads/master
Home: https://github.com/xwiki-contrib/book-versions
Commit: c81acdd94aa054388e27d1e6d908e12f05406376
https://github.com/xwiki-contrib/book-versions/commit/c81acdd94aa054388e27d…
Author: Raluca Stavro <rstavro(a)xwiki.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M application-book-versions-api/pom.xml
M application-book-versions-common-ui/pom.xml
M application-book-versions-default/pom.xml
M application-book-versions-publish-ui/pom.xml
M application-book-versions-ui/pom.xml
M application-book-versions-xip/pom.xml
M pom.xml
Log Message:
-----------
[maven-release-plugin] prepare release application-book-versions-1.23
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/book-versions/settings/notifications
Branch: refs/heads/stable-17.6.x
Home: https://github.com/xwiki/xwiki-platform
Commit: 9ddfc2194042181099b31b3f4c243e359ae12953
https://github.com/xwiki/xwiki-platform/commit/9ddfc2194042181099b31b3f4c24…
Author: Michael Hamann <michael.hamann(a)xwiki.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/main/java/org/xwiki/extension/security/internal/ExtensionSecurityScheduler.java
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/test/java/org/xwiki/extension/security/internal/ExtensionSecuritySchedulerTest.java
Log Message:
-----------
[Misc] Fix race condition blocking ExtensionSecuritySchedulerTest
* Fix a race condition where the future returned by
`ExtensionSecurityScheduler#start()` would
never be completed because it was null when the executor executed the
runnable. This can block the execution of
ExtensionSecuritySchedulerTest, causing it to hang infinitely. In
actual use, this could only happen when the extension security scan is
disabled as otherwise, the actual scan takes so much time that it's
unlikely that the completable future hasn't been initialized in the
meantime. Even for the disabled case, it seems very unlikely and most
likely not that problematic as the only code waiting for the
completable future seems to be testing code. It would prevent the
scheduler from executing again after 24h, but the only use case where
this would matter is if the scheduler was first disabled and then
re-enabled.
* Make ExtensionSecurityScheduler more robust by making `restart()`
synchronized, too.
* Bulletproof the test by only waiting 20 seconds for the future to be
completed.
(cherry picked from commit 8e31e99ee4182e3b23176317211774d912a3ee3b)
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications
Branch: refs/heads/stable-17.4.x
Home: https://github.com/xwiki/xwiki-platform
Commit: 8a766a69ad1b3650cb35840563cbee846378879e
https://github.com/xwiki/xwiki-platform/commit/8a766a69ad1b3650cb35840563cb…
Author: Michael Hamann <michael.hamann(a)xwiki.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/main/java/org/xwiki/extension/security/internal/ExtensionSecurityScheduler.java
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/test/java/org/xwiki/extension/security/internal/ExtensionSecuritySchedulerTest.java
Log Message:
-----------
[Misc] Fix race condition blocking ExtensionSecuritySchedulerTest
* Fix a race condition where the future returned by
`ExtensionSecurityScheduler#start()` would
never be completed because it was null when the executor executed the
runnable. This can block the execution of
ExtensionSecuritySchedulerTest, causing it to hang infinitely. In
actual use, this could only happen when the extension security scan is
disabled as otherwise, the actual scan takes so much time that it's
unlikely that the completable future hasn't been initialized in the
meantime. Even for the disabled case, it seems very unlikely and most
likely not that problematic as the only code waiting for the
completable future seems to be testing code. It would prevent the
scheduler from executing again after 24h, but the only use case where
this would matter is if the scheduler was first disabled and then
re-enabled.
* Make ExtensionSecurityScheduler more robust by making `restart()`
synchronized, too.
* Bulletproof the test by only waiting 20 seconds for the future to be
completed.
(cherry picked from commit 8e31e99ee4182e3b23176317211774d912a3ee3b)
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications
Branch: refs/heads/stable-16.10.x
Home: https://github.com/xwiki/xwiki-platform
Commit: 810b80eb2a8ca2238f8c26c8d2c3625e0bb672b9
https://github.com/xwiki/xwiki-platform/commit/810b80eb2a8ca2238f8c26c8d2c3…
Author: Michael Hamann <michael.hamann(a)xwiki.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/main/java/org/xwiki/extension/security/internal/ExtensionSecurityScheduler.java
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/test/java/org/xwiki/extension/security/internal/ExtensionSecuritySchedulerTest.java
Log Message:
-----------
[Misc] Fix race condition blocking ExtensionSecuritySchedulerTest
* Fix a race condition where the future returned by
`ExtensionSecurityScheduler#start()` would
never be completed because it was null when the executor executed the
runnable. This can block the execution of
ExtensionSecuritySchedulerTest, causing it to hang infinitely. In
actual use, this could only happen when the extension security scan is
disabled as otherwise, the actual scan takes so much time that it's
unlikely that the completable future hasn't been initialized in the
meantime. Even for the disabled case, it seems very unlikely and most
likely not that problematic as the only code waiting for the
completable future seems to be testing code. It would prevent the
scheduler from executing again after 24h, but the only use case where
this would matter is if the scheduler was first disabled and then
re-enabled.
* Make ExtensionSecurityScheduler more robust by making `restart()`
synchronized, too.
* Bulletproof the test by only waiting 20 seconds for the future to be
completed.
(cherry picked from commit 8e31e99ee4182e3b23176317211774d912a3ee3b)
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications
Branch: refs/heads/master
Home: https://github.com/xwiki/xwiki-platform
Commit: 8e31e99ee4182e3b23176317211774d912a3ee3b
https://github.com/xwiki/xwiki-platform/commit/8e31e99ee4182e3b231763172117…
Author: Michael Hamann <michael.hamann(a)xwiki.com>
Date: 2025-07-18 (Fri, 18 Jul 2025)
Changed paths:
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/main/java/org/xwiki/extension/security/internal/ExtensionSecurityScheduler.java
M xwiki-platform-core/xwiki-platform-extension/xwiki-platform-extension-security/xwiki-platform-extension-security-index/src/test/java/org/xwiki/extension/security/internal/ExtensionSecuritySchedulerTest.java
Log Message:
-----------
[Misc] Fix race condition blocking ExtensionSecuritySchedulerTest
* Fix a race condition where the future returned by
`ExtensionSecurityScheduler#start()` would
never be completed because it was null when the executor executed the
runnable. This can block the execution of
ExtensionSecuritySchedulerTest, causing it to hang infinitely. In
actual use, this could only happen when the extension security scan is
disabled as otherwise, the actual scan takes so much time that it's
unlikely that the completable future hasn't been initialized in the
meantime. Even for the disabled case, it seems very unlikely and most
likely not that problematic as the only code waiting for the
completable future seems to be testing code. It would prevent the
scheduler from executing again after 24h, but the only use case where
this would matter is if the scheduler was first disabled and then
re-enabled.
* Make ExtensionSecurityScheduler more robust by making `restart()`
synchronized, too.
* Bulletproof the test by only waiting 20 seconds for the future to be
completed.
To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications