Branch: refs/heads/architecture-reserve-entry-needs-note Home: https://github.com/xwiki-contrib/application-releasenotes Commit: 6341c1ae6eba4bf62da72f352d07314c91079271 https://github.com/xwiki-contrib/application-releasenotes/commit/6341c1ae6eb... Author: Vincent Massol <[email protected]> Date: 2026-09-30 (Wed, 30 Sep 2026) Changed paths: M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/internal/ReleaseNotesEntryPoint.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/script/ReleaseNotesScriptService.java M application-releasenotes-api/src/test/java/org/xwiki/contrib/releasenotes/internal/ReleaseNotesEntryPointTest.java M application-releasenotes-ui/src/main/resources/ReleaseNotes/Code/EntryVelocityMacros.xml M application-releasenotes-ui/src/main/resources/ReleaseNotes/Code/Translations.xml M application-releasenotes-ui/src/test/java/org/xwiki/contrib/releasenotes/AddChangePageTest.java Log Message: ----------- RN-131: A script can create a change for a release note that does not exist * Refuse to reserve the page of a new entry under a release note that does not exist, as createChange already does: the checks go through ReleaseNotesEntryPoint, the managers still check no right * Tell the author of an "add change" form that the release note does not exist, instead of the generic failure * Test it on the entry point and on handleAddAction Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/application-releasenotes/settings/notificat...