September 2026 - notifications

[[email protected]][Issue] Updates for XWIKI-24762: Add a page object for the Live Data Properties advanced panel
by XWiki Notifications 10 Sep '26

10 Sep '26

1 0

[xwiki-contrib/application-releasenotes] ee26ae: RN-119: A change cannot be updated once created, s...
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/RN-119 Home: https://github.com/xwiki-contrib/application-releasenotes Commit: ee26ae5273cd25f364f5440036017f444662c5c7 https://github.com/xwiki-contrib/application-releasenotes/commit/ee26ae5273… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M application-releasenotes-api/pom.xml M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/ChangeManager.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/ReleaseNoteManager.java A application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/ReleaseNotesNotFoundException.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/internal/DefaultChangeManager.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/internal/DefaultReleaseNoteManager.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/DefaultChangeManagerTest.java M application-releasenotes-api/src/test/java/org/xwiki/contrib/releasenotes/internal/DefaultReleaseNoteManagerTest.java M application-releasenotes-api/src/test/java/org/xwiki/contrib/releasenotes/script/ReleaseNotesScriptServiceTest.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/ChangeResource.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/ReleaseNoteResource.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/AbstractReleaseNotesResource.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultChangeResource.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultChangesResource.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultReleaseNoteResource.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/ReleaseNotesExceptionMapper.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/RepresentationFactory.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/model/ChangeRepresentation.java M application-releasenotes-rest/src/main/resources/META-INF/components.txt A application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultChangeResourceTest.java A application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultReleaseNoteResourceTest.java M application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/ReleaseNotesExceptionMapperTest.java M application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/RepresentationFactoryTest.java M application-releasenotes-test/application-releasenotes-test-docker/src/test/it/org/xwiki/contrib/releasenotes/test/ui/ReleaseNotesRestClient.java M application-releasenotes-test/application-releasenotes-test-docker/src/test/it/org/xwiki/contrib/releasenotes/test/ui/ReleaseNotesRestIT.java Log Message: ----------- RN-119: A change cannot be updated once created, so its screenshots cannot be set over REST * Add `PUT` and `GET` on one release note and on one change, so the two properties that could not be written after creation now can: the `screenshots` of a change, which name attachments of a page the `POST` itself allocates, and the `released`/`date` of a release note, which are known on the day the version ships. * A change is addressed by its entry page name, `.../changes/Entry001`, which `ChangeRepresentation` now answers as `entry` so a client never parses it out of a page reference. * A `PUT` replaces: the stored release note or change becomes exactly what the request carries, and a property the request leaves out is emptied rather than kept. The templates apply to creation only. * The product and the version are not replaced by either: they locate the page, so changing them would be a move rather than an update. * Add `ChangeManager#updateChange` and `ReleaseNoteManager#updateReleaseNote`, both answering what is stored once replaced, and expose them on the script service. * Add `ReleaseNotesNotFoundException`, thrown when a page holds no change or no release note and mapped to a `404`, which is what the two `GET`s and the two `PUT`s answer with. * Modify a copy of the page rather than the instance the store cached, since these are the first writes of the application to a page that already exists. * Ignore the two `java.method.addedToInterface` differences in Revapi: both roles are `@Unstable` and this repository holds their only implementations. * `ReleaseNotesRestIT` walks the flow the issue is about, from creating a change through attaching its image to naming it, and the `-api` JaCoCo ratio moves to 0.95 for the two store-failure blocks the test store cannot reach. 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-contrib/application-releasenotes/settings/notifica…

1 0

[xwiki-contrib/application-releasenotes] 668962: RN-119: A change cannot be updated once created, s...
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/RN-119 Home: https://github.com/xwiki-contrib/application-releasenotes Commit: 668962be4096db70c46fe5a91549fa56b5487890 https://github.com/xwiki-contrib/application-releasenotes/commit/668962be40… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M application-releasenotes-api/pom.xml M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/ChangeManager.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/ReleaseNoteManager.java A application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/ReleaseNotesNotFoundException.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/internal/DefaultChangeManager.java M application-releasenotes-api/src/main/java/org/xwiki/contrib/releasenotes/internal/DefaultReleaseNoteManager.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/DefaultChangeManagerTest.java M application-releasenotes-api/src/test/java/org/xwiki/contrib/releasenotes/internal/DefaultReleaseNoteManagerTest.java M application-releasenotes-api/src/test/java/org/xwiki/contrib/releasenotes/script/ReleaseNotesScriptServiceTest.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/ChangeResource.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/ReleaseNoteResource.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/AbstractReleaseNotesResource.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultChangeResource.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultChangesResource.java A application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultReleaseNoteResource.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/ReleaseNotesExceptionMapper.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/internal/RepresentationFactory.java M application-releasenotes-rest/src/main/java/org/xwiki/contrib/releasenotes/rest/model/ChangeRepresentation.java M application-releasenotes-rest/src/main/resources/META-INF/components.txt A application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultChangeResourceTest.java A application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/DefaultReleaseNoteResourceTest.java M application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/ReleaseNotesExceptionMapperTest.java M application-releasenotes-rest/src/test/java/org/xwiki/contrib/releasenotes/rest/internal/RepresentationFactoryTest.java M application-releasenotes-test/application-releasenotes-test-docker/src/test/it/org/xwiki/contrib/releasenotes/test/ui/ReleaseNotesRestClient.java M application-releasenotes-test/application-releasenotes-test-docker/src/test/it/org/xwiki/contrib/releasenotes/test/ui/ReleaseNotesRestIT.java Log Message: ----------- RN-119: A change cannot be updated once created, so its screenshots cannot be set over REST * Add `PUT` and `GET` on one release note and on one change, so the two properties that could not be written after creation now can: the `screenshots` of a change, which name attachments of a page the `POST` itself allocates, and the `released`/`date` of a release note, which are known on the day the version ships. * A change is addressed by its entry page name, `.../changes/Entry001`, which `ChangeRepresentation` now answers as `entry` so a client never parses it out of a page reference. * A `PUT` replaces: the stored release note or change becomes exactly what the request carries, and a property the request leaves out is emptied rather than kept. The templates apply to creation only. * The product and the version are not replaced by either: they locate the page, so changing them would be a move rather than an update. * Add `ChangeManager#updateChange` and `ReleaseNoteManager#updateReleaseNote`, both answering what is stored once replaced, and expose them on the script service. * Add `ReleaseNotesNotFoundException`, thrown when a page holds no change or no release note and mapped to a `404`, which is what the two `GET`s and the two `PUT`s answer with. * Modify a copy of the page rather than the instance the store cached, since these are the first writes of the application to a page that already exists. * Ignore the two `java.method.addedToInterface` differences in Revapi: both roles are `@Unstable` and this repository holds their only implementations. * `ReleaseNotesRestIT` walks the flow the issue is about, from creating a change through attaching its image to naming it, and the `-api` JaCoCo ratio moves to 0.95 for the two store-failure blocks the test store cannot reach. 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-contrib/application-releasenotes/settings/notifica…

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/tags/v1.9.1 Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 237236: [Misc] Release 1.9.1
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 237236a0448f6a8fa2b3b8780d03437a958a80c0 https://github.com/xwiki/xwiki-dev-llm/commit/237236a0448f6a8fa2b3b8780d034… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json Log Message: ----------- [Misc] Release 1.9.1 * content edits only (no capability added or removed) To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/release-doc-skill-bugfix-and-noteworthiness Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] d2e53d: [Misc] Make the release-documentation sweep surviv...
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: d2e53d041f1c621684ed8628f24f98206ecbb71f https://github.com/xwiki/xwiki-dev-llm/commit/d2e53d041f1c621684ed8628f24f9… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M xwiki/skills/xwiki-release-documentation/SKILL.md Log Message: ----------- [Misc] Make the release-documentation sweep survive a bugfix release Three corrections found by running the skill for real, over the 17 issues fixed in 17.10.13. * Say what a bugfix release does with entries. For an X.Y.Z with Z > 0 the release-note page renders {{jira}} instead of {{releasenotechanges/}}, so an entry posted against that version is stored and never rendered. That is a fact about the page, not about the issues: a bugfix release is mostly bug fixes, which go to N/A on their own merits, but improvements do get slipped in when they are what fixes the bug and those need their entry like any other — against the .0 or RC version the issue is also fixed in, which is where it renders. Every improvement of the recent bugfix releases that carries an entry URL points there, and no bugfix note stores an entry. * Search the identifiers the diff touches, not only the subject. The subject search answers "is there a page about this feature", which for a fix is usually "no" — and that "no" was being read as the documentation verdict. Searching the strings in the diff instead surfaced a page whose subject was a MySQL error but which carried one incidental sentence about the very statement the fix changed. * Replace the Bug trigger "user-visible behaviour or public API changed" with noteworthiness. Nearly every bug fix changes user-visible behaviour, that being what made it a bug, so the old wording fired on all of them. Add the query that measures the bar the project actually applies. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 394209f15ac959aefff07a697b9c5d5ad20adebe https://github.com/xwiki/xwiki-dev-llm/commit/394209f15ac959aefff07a697b9c5… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M xwiki/skills/xwiki-release-documentation/SKILL.md Log Message: ----------- Merge pull request #127 from xwiki/release-doc-skill-bugfix-and-noteworthiness [Misc] Make the release-documentation sweep survive a bugfix release Compare: https://github.com/xwiki/xwiki-dev-llm/compare/c9eef0aa93c3...394209f15ac9 To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] d2e53d: [Misc] Make the release-documentation sweep surviv...
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/release-doc-skill-bugfix-and-noteworthiness Home: https://github.com/xwiki/xwiki-dev-llm Commit: d2e53d041f1c621684ed8628f24f98206ecbb71f https://github.com/xwiki/xwiki-dev-llm/commit/d2e53d041f1c621684ed8628f24f9… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M xwiki/skills/xwiki-release-documentation/SKILL.md Log Message: ----------- [Misc] Make the release-documentation sweep survive a bugfix release Three corrections found by running the skill for real, over the 17 issues fixed in 17.10.13. * Say what a bugfix release does with entries. For an X.Y.Z with Z > 0 the release-note page renders {{jira}} instead of {{releasenotechanges/}}, so an entry posted against that version is stored and never rendered. That is a fact about the page, not about the issues: a bugfix release is mostly bug fixes, which go to N/A on their own merits, but improvements do get slipped in when they are what fixes the bug and those need their entry like any other — against the .0 or RC version the issue is also fixed in, which is where it renders. Every improvement of the recent bugfix releases that carries an entry URL points there, and no bugfix note stores an entry. * Search the identifiers the diff touches, not only the subject. The subject search answers "is there a page about this feature", which for a fix is usually "no" — and that "no" was being read as the documentation verdict. Searching the strings in the diff instead surfaced a page whose subject was a MySQL error but which carried one incidental sentence about the very statement the fix changed. * Replace the Bug trigger "user-visible behaviour or public API changed" with noteworthiness. Nearly every bug fix changes user-visible behaviour, that being what made it a bug, so the old wording fired on all of them. Add the query that measures the bar the project actually applies. 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-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] e355c5: [Misc] Make the release-documentation sweep surviv...
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/heads/release-doc-skill-bugfix-and-noteworthiness Home: https://github.com/xwiki/xwiki-dev-llm Commit: e355c58e301ffb48932104250af43818db3d06af https://github.com/xwiki/xwiki-dev-llm/commit/e355c58e301ffb48932104250af43… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-10 (Thu, 10 Sep 2026) Changed paths: M xwiki/skills/xwiki-release-documentation/SKILL.md Log Message: ----------- [Misc] Make the release-documentation sweep survive a bugfix release Three corrections found by running the skill for real, over the 17 issues fixed in 17.10.13. * Say that a bugfix release takes no entries. For an X.Y.Z with Z > 0 the release-note page renders {{jira}} instead of {{releasenotechanges/}}, so an entry posted there is stored and never rendered. The OKF said this; the skill did not act on it, and the sweep spent its triage proposing entries that could not appear. State where an entry would go instead (the .0 RC in the issue's Fix Version list) while making clear that this licenses no entry by itself, and that an already-released RC means a retroactive edit. * Search the identifiers the diff touches, not only the subject. The subject search answers "is there a page about this feature", which for a fix is usually "no" — and that "no" was being read as the documentation verdict. Searching the strings in the diff instead surfaced a page whose subject was a MySQL error but which carried one incidental sentence about the very statement the fix changed. * Replace the Bug trigger "user-visible behaviour or public API changed" with noteworthiness. Nearly every bug fix changes user-visible behaviour, that being what made it a bug, so the old wording fired on all of them. Add the query that measures the bar the project actually applies. 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-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 10 Sep '26

10 Sep '26

Branch: refs/tags/v1.9.0 Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0