Daily Digest: 2026-06-05

[github-actions]

We are given a daily digest for 2026-06-05. We need to structure the response as:

1. Highlights (1-3 bullet points of the most important changes)
2. Code Changes (summarize commits by theme, not individually)
3. Pull Requests (merged, opened, pending review)
4. Issues (new, closed, total open)
5. Repository Health (stars, forks, CI status)
6. Action Items (anything that needs attention: failing CI, stale PRs, unanswered issues)

Let's break down the provided data:

Repository Stats

• Stars: 90
• Forks: 31
• Watchers: 6
• Open issues: 1 (but note: the issues section lists several opened and closed, so we'll compute total open from the issues data)

Commits (last 24h)

There are 10 commits, all by Andrej Koelewijn, and they are all fixes (mostly for the describe command, but also for OQL and pages). The themes are:

• Fixes for the describe command (round-trip issues):
  • widget-action microflow args (commit f12269d)
  • reserved-keyword datagrid column names (d02283e)
  • java-action body (22221f6)
  • microflow/nanoflow for widget actions (5bbc070)
  • bare grant member names (426a33c)
• Fixes for OQL:
  • surface 11.11 dev-endpoint query errors (9631dab)
  • support Mendix 11.11 /dev/preview_execute_oql endpoint (4b38bfd)
• Fixes for pages:
  • allow reserved-keyword page/snippet param names via quoting (54e80d0)
  • allow reserved-keyword widget names via quoting (8398d6c)
• Documentation: finalize v0.12.0 changelog (932cd9d)

Pull Requests Merged (last 24h)

• None.

Pull Requests Opened (last 24h)

• None.

Currently Open PRs

• fix #595: PublishedODataService EntityTypePointer wired by qualified entity name #596: fix PublishedODataService EntityTypePointer never set — Studio Pro NRE in EntitySet.Check #595: PublishedODataService EntityTypePointer wired by qualified entity name
• fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592: fix 10-odata-examples.mdl Level 9.1 crashes Studio Pro project check (NRE in CallExternalAction.SchemaAction) #590: rewrite OData example Level 9.1 to use TripPin schema actions
• docs: add manual test case documentation for all MDL command areas #386: docs: add manual test case documentation for all MDL command areas

Issues Opened (last 24h)

• -p <project> C-escapes Windows backslash paths -> 'unable to open database file' #644: -p C-escapes Windows backslash paths -> 'unable to open database file'
• Datasource-typed pluggable-widget property passes 'check' but is silently dropped at 'exec' (CE0642) #643: Datasource-typed pluggable-widget property passes 'check' but is silently dropped at 'exec' (CE0642)
• XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply #641: XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply
• Quoted where '<xpath>' mis-stores every constraint (CE0161); only inline where [...] works #642: Quoted where '<xpath>' mis-stores every constraint (CE0161); only inline where [...] works

Issues Closed (last 24h)

• DESCRIBE emits widget-action microflow args as 'Name = value' but grammar wants 'Name: value' (roundtrip break) #640: DESCRIBE emits widget-action microflow args as 'Name = value' but grammar wants 'Name: value' (roundtrip break)
• Daily Digest: 2026-06-04 #639: Daily Digest: 2026-06-04 (this is a digest issue, not a bug)
• DESCRIBE emits unquoted reserved-keyword datagrid column names (e.g. 'column Title'), which fails to re-parse — #619 missed columns #638: DESCRIBE emits unquoted reserved-keyword datagrid column names (e.g. 'column Title'), which fails to re-parse — DESCRIBE output emits unquoted reserved-word identifiers that fail mxcli check #619 missed columns
• DESCRIBE emits body-less CREATE JAVA ACTION for source-less (add-on module) actions, which fails to re-parse (roundtrip break) #637: DESCRIBE emits body-less CREATE JAVA ACTION for source-less (add-on module) actions, which fails to re-parse (roundtrip break)
• Daily Digest: 2026-06-03 #635: Daily Digest: 2026-06-03
• DESCRIBE emits action: call_microflow/call_nanoflow for widget actions, which the parser rejects (roundtrip break) #634: DESCRIBE emits action: call_microflow/call_nanoflow for widget actions, which the parser rejects (roundtrip break)
• DESCRIBE emits over-qualified grant member names that fail to re-parse (roundtrip break) #633: DESCRIBE emits over-qualified grant member names that fail to re-parse (roundtrip break)
• ALTER STYLING cannot set design properties on widgets in pages and snippets #631: ALTER STYLING cannot set design properties on widgets in pages and snippets
• Reserved words can't be used as SHOW_PAGE parameter names #114: Reserved words can't be used as SHOW_PAGE parameter names

Note: The digest issues (#639, #635) are not real issues but are likely automated digests. We should ignore them for the purpose of counting real issues.

CI Status (latest runs on main)

• Daily Project Digest [2026-06-05T10:41:25Z] -> success (implied by the dash? Actually, the first one is shown as " — " which might mean skipped or not run? But the next two are failure and skipped. Let's read:
  • — Daily Project Digest [2026-06-05T10:41:25Z] (this is the current digest run, and it's shown as a dash, meaning it's the one we are generating? So we can ignore it for health)
  • failure — Nightly Release & Integration Tests [2026-06-05T06:42:36Z]
  • skipped — Enhancement Guide [2026-06-05T00:23:36Z]

So the Nightly Release & Integration Tests is failing.

Dependency Changes

• None.

Now, let's structure the response:

Highlights

We have a lot of fixes for the describe command (round-trip issues) and also for OQL and pages. The most important might be the round-trip fixes for DESCRIBE because they break the ability to round-trip (describe then apply). Also, the OQL fixes for Mendix 11.11 are important for compatibility.

But note: the digest is for 2026-06-05, and the commits are from 2026-06-04 (as per the first commit message: "docs(changelog): finalize v0.12.0 (2026-06-04)").

We can highlight:

• Multiple fixes for DESCRIBE round-trip issues (widget actions, reserved keywords, java-action body, grant members) ensuring that DESCRIBE output can be reapplied without errors.
• OQL support updated for Mendix 11.11, including error handling and endpoint changes.
• Pages: reserved keywords in parameter and widget names now supported via quoting.

Code Changes

We can group by theme:

• DESCRIBE command: fixed round-trip issues for widget-action args, reserved-keyword column names, java-action body, widget action microflow/nanoflow emission, and grant member names.
• OQL: improved error handling for Mendix 11.11 dev-endpoint and added support for the new /dev/preview_execute_oql endpoint.
• Pages: allowed reserved keywords in page/snippet parameter names and widget names via quoting.
• Documentation: finalized changelog for v0.12.0.

Pull Requests

• Merged: none in the last 24h.
• Opened: none in the last 24h.
• Pending review: 3 open PRs (fix #595: PublishedODataService EntityTypePointer wired by qualified entity name #596, fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592, docs: add manual test case documentation for all MDL command areas #386).

Issues

• New issues (last 24h): 4 (-p <project> C-escapes Windows backslash paths -> 'unable to open database file' #644, Datasource-typed pluggable-widget property passes 'check' but is silently dropped at 'exec' (CE0642) #643, XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply #641, Quoted where '<xpath>' mis-stores every constraint (CE0161); only inline where [...] works #642). Note: we ignore the digest issues (Daily Digest: 2026-06-04 #639, Daily Digest: 2026-06-03 #635) as they are not real.

• Closed issues (last 24h): 9, but note that two of them are digest issues (Daily Digest: 2026-06-04 #639, Daily Digest: 2026-06-03 #635) and the rest are real fixes. However, for the digest we just report the numbers as given.
  But the instruction says: "Issues (new, closed, total open)". We have:
  New: 4
  Closed: 9 (as per the list, but note that the list includes two digests, but we are to use the provided data)
  However, the repository stats said "Open issues: 1", which doesn't match. Let's check:

  The repository stats table says "Open issues: 1", but we have 4 new issues opened in the last 24h and several closed. This suggests that the "Open issues" in the stats might be outdated or we are to compute from the issues.

  Actually, the problem says: "Repository Stats" at the top, which includes "Open issues: 1". But then in the issues section we see new and closed. We should use the provided stats for the repository health, and for the issues section we report the new and closed as given.

  However, note that the repository stats might be as of the beginning of the day? We are to report the current state.

  Let's compute total open issues from the data:
  We started with some open issues, then we had 4 new and 9 closed (but note: the closed list includes two that are digests, which might not be real issues?).

  But the instruction for the digest is to report:
  Issues (new, closed, total open)

  We are given:
  New: 4
  Closed: 9 (as per the list)

  And the repository stats says Open issues: 1. This is conflicting.

  However, looking at the closed issues, we see Daily Digest: 2026-06-04 #639 and Daily Digest: 2026-06-03 #635 are digests (which are likely automated and closed immediately). So if we subtract those, we have 7 real issues closed. But we don't know the starting point.

  Since the repository stats provided at the top says "Open issues: 1", we will use that for the total open in the Issues section? But the instruction says to report new, closed, and total open.

  Let me re-read: "Issues (new, closed, total open)"

  We have:
  new: 4
  closed: 9 (from the list)
  total open: we don't have a direct number, but the repository stats says 1.

  However, note that the repository stats might be the current state. So we can use:
  total open: 1 (from the repository stats)

  But then how do we reconcile? It's possible that the 4 new issues and 9 closed issues are from the last 24h, and the total open is 1 (meaning that before the last 24h there were 6 open issues, then we added 4 and closed 9, so 6+4-9=1).

  So we'll report:
  New: 4
  Closed: 9
  Total open: 1

Repository Health

• Stars: 90

• Forks: 31

• CI Status:

  • Nightly Release & Integration Tests: failure (last run 2026-06-05T06:42:36Z)
  • Enhancement Guide: skipped
  • Daily Project Digest: (we are generating this, so we can ignore or note as success? It's shown as a dash, but it's the current run so we don't have a status yet? Actually, the digest run is the one that is generating this report, so it's in progress? But the timestamp is 10:41:25Z, which is in the future relative to the nightly run? We are to report the latest runs on main. We have three runs: one success? (the digest run is shown as a dash, which might mean it's not completed? But the timestamp is given, so it completed. However, the status is not shown with a word, just a dash. Let's assume the dash means it passed? But the next two have words: failure and skipped.

  Actually, the format is:
  [status] — [description] [timestamp]

  For the first one: " — Daily Project Digest [2026-06-05T10:41:25Z]" -> the status is missing? It might be that the status is implied by the dash? But the second one has "failure —", so the first one might be skipped? Or it's the current digest and we don't have a status?

  Since we are generating the digest, we can note that the Nightly Release & Integration Tests is failing, which needs attention.

Action Items

• The Nightly Release & Integration Tests is failing (last run). This needs investigation.
• There are 3 open PRs that are stale? We don't have the exact age, but docs: add manual test case documentation for all MDL command areas #386 is old (from the number). We should check if any PRs are stale (e.g., no activity for a long time). However, we don't have the dates. But note: the digest is daily, so we can note that there are open PRs that need review.
• Also, we have 4 new issues that need to be triaged.

But note: the instruction says "anything that needs attention: failing CI, stale PRs, unanswered issues"

We have:

• Failing CI: Nightly Release & Integration Tests
• Stale PRs: we don't have the exact age, but we can note that there are 3 open PRs (the oldest being docs: add manual test case documentation for all MDL command areas #386) and they might need review.
• Unanswered issues: 4 new issues (from the last

---

Daily digest generated automatically — workflow source