September 2026 - notifications

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

18 Sep '26

Branch: refs/heads/ci-check-cross-branch 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] 7efd15: [Misc] Treat one break on four branches as one break
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-cross-branch Home: https://github.com/xwiki/xwiki-dev-llm Commit: 7efd1562b14fc88b5dd3726834eee140b9a22ff8 https://github.com/xwiki/xwiki-dev-llm/commit/7efd1562b14fc88b5dd3726834eee… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Treat one break on four branches as one break * Group incidents by repo and signature across branches: `alsoOn` names the other branches, `crossBranch` is `also-red`, and `primary` marks the one incident that carries the analysis, the comment and the paste's entry. The others are named on its line, with their own regression windows, and are analysed nowhere. * Add the `fixed-elsewhere` fix state: the same failure red on another maintained branch and green there now, with the commit that did it — a backport candidate to hand to `xwiki-backport`, never a backport this skill opens. * Require, before claiming a fix elsewhere, two consecutive failures and then two consecutive passes on that branch, the test still running there, and a commit that touches the failing file. Measured over three branches: the naive "failed, passes now" rule fires five times, all of them flickers passing; this one fires once. * Refuse the pass for a quality gate and for an unclassified break: a gate fails on aggregate metrics, and the first live run duly offered an unrelated bug fix from a third branch as its fix. * Key `flickerGroup` on the repo and the test class alone, so one flaky suite is one issue whatever branch and window each method was seen on. * Fetch a build's test report once per run, for the history walk, the flicker rating and the cross-branch check alike. 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] b49093: [Misc] Say only what moved since the last CI digest
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-delta-digest Home: https://github.com/xwiki/xwiki-dev-llm Commit: b4909367e15f4014aa8692caba51c186fc1da63b https://github.com/xwiki/xwiki-dev-llm/commit/b4909367e15f4014aa8692caba51c… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M README.md M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs M xwiki/skills/xwiki-ci-check/tools/matrix.mjs Log Message: ----------- [Misc] Say only what moved since the last CI digest * The daily digest is a delta, not a state snapshot: a snapshot of what is red this morning is what the CI dashboard already is, and a reader who gets it faster there stops reading the digest. A morning that moved nothing is now not posted at all, and what went green — the one thing a dashboard can never show — gets its own line. * The Matrix room is the ledger: each digest carries the state of every incident it covers in a base64 marker appended to its `formatted_body`, which no client renders and no bridge relays. Nothing is stored anywhere, so the routine's sandbox can stay new every morning. * `matrix.mjs --last-digest` / `--last-state` read the bot's own most recent message back, filtered on the sender server-side and following the continuation token, and `--state <delta.json>` carries today's forward. * `ci-check.mjs --delta <work-order> --previous <state>` classifies each incident NEW / CHANGED / FIXED / SAME. It reads two files and no server. * An unreadable room classifies nothing rather than calling everything new, and the digest falls back to the full snapshot saying why: a routine silenced by a failed read is indistinguishable from a green morning. * Incidents beyond the blame horizon are counted and never compared — an old flicker that fails every other day would otherwise produce a FIXED line and a NEW line every other morning. 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 18 Sep '26

18 Sep '26

Branch: refs/tags/v1.12.5 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] 3bc87b: [Misc] Release 1.12.5
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 3bc87b2617690f2e4a4830d4b45d83c9b8319cf3 https://github.com/xwiki/xwiki-dev-llm/commit/3bc87b2617690f2e4a4830d4b45d8… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-18 (Fri, 18 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.12.5 * 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 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-stale-snapshot 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] acda60: [Misc] Stay quiet about an Environment Tests run t...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: acda60a5b3aedca5d01f11a6ffd71fdcbcedd65a https://github.com/xwiki/xwiki-dev-llm/commit/acda60a5b3aedca5d01f11a6ffd71… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about an Environment Tests run that used stale jars * Add `stale-snapshot` to `fixState`. The Environment Tests job builds only the test modules it was given and takes the rest of its WAR from the last snapshot deployed to Nexus, so a commit carrying a test *and* the production code that test needs is red there until the next deployment — with stack-trace line numbers read from the old file, which is exactly what a defect in the new test looks like. * Bound the snapshot by build revisions rather than by parsing a log: XWiki's CI runs Maven without transfer progress, so no build log names a resolved artifact (measured on Environment Tests `#1377`: 192 KB of step console, no download line, and the wfapi node log serves only a 10 KiB tail anyway). Two `buildRevision` calls and one compare, no Nexus call, no `consoleText`. * Take the revision of the most recent *completed* main build that had started when the environment build did — an upper bound, since a build still running has deployed nothing. Erring detects less, which is the direction a detector that buys silence must fail in. Not the last *green* one: platform's main job has been `FAILURE` on every build for days, the quality gate running after the deploy, so a green one would date the snapshot to last week. * Require one commit in that gap to touch the failing test class *and* a production file. A test change here and a production change there is an ordinary pair of commits, and reading it as the trap would silence a real breakage on a coincidence. Page objects and the docker test framework are not production: the job builds those. * Evaluate it before the forward-fix and in-flight gates. It is the only value of the three that says the test was never broken, and reporting a fix for it implies there was something to fix. * Set it only for a test failing in the environment job alone — the main job builds everything from source, so a test red there is red for real — which needs the new `failingJobs` field, `window.job` naming only the job that saw it break first. And only where the incident's first bad build is the build being examined: one that survived the next run met jars that had caught up. Verified against xwiki-platform/master, where Environment Tests `#1377` started 13 minutes after a commit that pushed `VersionIT` and `XWikiHibernateVersioningStore` together, and the incident that S1 reported as "possibly fixed already" now reads as the trap it is. The two blocknote flickers pass every guard and stay `null`, no commit in the gap naming them. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: b4d19df9ddb9a9e73e475b9bd1b1cb5f718958c8 https://github.com/xwiki/xwiki-dev-llm/commit/b4d19df9ddb9a9e73e475b9bd1b1c… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- Merge pull request #153 from xwiki/ci-check-stale-snapshot [Misc] Stay quiet about an Environment Tests run that used stale jars Compare: https://github.com/xwiki/xwiki-dev-llm/compare/e26dfc84128b...b4d19df9ddb9 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] acda60: [Misc] Stay quiet about an Environment Tests run t...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-stale-snapshot Home: https://github.com/xwiki/xwiki-dev-llm Commit: acda60a5b3aedca5d01f11a6ffd71fdcbcedd65a https://github.com/xwiki/xwiki-dev-llm/commit/acda60a5b3aedca5d01f11a6ffd71… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about an Environment Tests run that used stale jars * Add `stale-snapshot` to `fixState`. The Environment Tests job builds only the test modules it was given and takes the rest of its WAR from the last snapshot deployed to Nexus, so a commit carrying a test *and* the production code that test needs is red there until the next deployment — with stack-trace line numbers read from the old file, which is exactly what a defect in the new test looks like. * Bound the snapshot by build revisions rather than by parsing a log: XWiki's CI runs Maven without transfer progress, so no build log names a resolved artifact (measured on Environment Tests `#1377`: 192 KB of step console, no download line, and the wfapi node log serves only a 10 KiB tail anyway). Two `buildRevision` calls and one compare, no Nexus call, no `consoleText`. * Take the revision of the most recent *completed* main build that had started when the environment build did — an upper bound, since a build still running has deployed nothing. Erring detects less, which is the direction a detector that buys silence must fail in. Not the last *green* one: platform's main job has been `FAILURE` on every build for days, the quality gate running after the deploy, so a green one would date the snapshot to last week. * Require one commit in that gap to touch the failing test class *and* a production file. A test change here and a production change there is an ordinary pair of commits, and reading it as the trap would silence a real breakage on a coincidence. Page objects and the docker test framework are not production: the job builds those. * Evaluate it before the forward-fix and in-flight gates. It is the only value of the three that says the test was never broken, and reporting a fix for it implies there was something to fix. * Set it only for a test failing in the environment job alone — the main job builds everything from source, so a test red there is red for real — which needs the new `failingJobs` field, `window.job` naming only the job that saw it break first. And only where the incident's first bad build is the build being examined: one that survived the next run met jars that had caught up. Verified against xwiki-platform/master, where Environment Tests `#1377` started 13 minutes after a commit that pushed `VersionIT` and `XWikiHibernateVersioningStore` together, and the incident that S1 reported as "possibly fixed already" now reads as the trap it is. The two blocknote flickers pass every guard and stay `null`, no commit in the gap naming them. 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 18 Sep '26

18 Sep '26

Branch: refs/tags/v1.12.4 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] e26dfc: [Misc] Release 1.12.4
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: e26dfc84128bff59190bfed6826523ced339f67e https://github.com/xwiki/xwiki-dev-llm/commit/e26dfc84128bff59190bfed682652… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-18 (Fri, 18 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.12.4 * 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