Daily Digest: 2026-06-22

[github-actions]

We are given a daily digest for 2026-06-22. 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: 94
• Forks: 31
• Watchers: 5
• Open issues: 1 (but note: the issues section will give more detail)

Commits (last 24h)

We have 9 commits. Let's group them by theme:

• Widgets:
  • 52542fb5: fix(widgets): register all widgets in a bundled .mpk (issue Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) #679)
• Documentation:
  • c96b2544: docs(changelog): v0.14.0 — JavaScript actions, clickable containers, XPath fixes
  • 3b07ec40: docs(javascript-actions): add user skill + site reference page
• Pages:
  • f115580d: fix(pages): preserve qualified enum literal in conditional Visible/Editable (regression)
  • 7ba439c2: fix(pages): support clickable CONTAINER OnClick action (issue The click property on the Container is not supported by the MDL parser #603)
• XPath:
  • 561f674c: fix(xpath): quote bare [%token%] inside bracketed constraints (Issue 641)
  • f61b3deb: feat(check): flag System.owner XPath refs on entities without owner stored (Issue 641)
• Check:
  • f2dca12e: fix(check): renumber issue-643 widget rules to MDL-WIDGET05/06
• JavaScript Actions:
  • 9065d71b: feat(javascript-actions): CREATE/DROP JAVASCRIPT ACTION (both engines)

Pull Requests Merged (last 24h)

• None

Pull Requests Opened (last 24h)

• None

Currently Open PRs

• #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 (@ako)
• #386: docs: add manual test case documentation for all MDL command areas (@retran)

Issues Opened (last 24h)

• #680: CREATE JAVA ACTION cannot create Enumeration parameter — serialized as entity ref, build fails ('selected entity no longer exists') (@Chendodelangen)
• #679: Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) (@ako)
• #677: Regression (v0.13.0): enum literal in conditional Visible/Editable expression mangled to a string → CE0117 (@ako)

Issues Closed (last 24h)

• #678: Daily Digest: 2026-06-21
• #641: XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply

CI Status (latest runs on main)

• Daily Project Digest [2026-06-22T12:44:06Z] (status not explicitly given, but the format shows a dash for the first one? Actually, it's listed as:

  • — Daily Project Digest 2026-06-22T12:44:06Z
  • success — AI Issue Review 2026-06-22T11:24:43Z
  • skipped — Enhancement Guide 2026-06-22T11:24:31Z

  So the first one (Daily Project Digest) has no status indicated? But note: the dash might mean it's not set or failed? However, in the context, we are to report CI status. Since the first one is the digest run and it's not marked as success, we should note it. But looking at the data, it's presented as a blank. However, in the repository, the digest run might be a custom action that we don't have status for? But the instruction says: "CI Status (latest runs on main)".

  Let's interpret:

  • The first run (Daily Project Digest) has no status symbol (just a dash) -> we can consider it as unknown or failed? But note: the other two have "success" and "skipped". Since the digest run is the one we are generating, it might be that the action is still running or failed? However, the timestamp is 12:44:06Z and the current time of the digest is 2026-06-22, so it's likely that the digest run has completed. But the data doesn't show a status.

  Given the ambiguity, we'll note that the Daily Project Digest run does not have a success status indicated (it's blank). However, in the context of the problem, we are to report what we see.

  Alternatively, the blank might be a formatting error. But we have to go by what's given.

  We'll report:

  • Daily Project Digest: (no status shown) -> we'll note it as not successful? But the instruction says to keep concise.

  Since the other two are success and skipped, and the digest run is the one we are generating, it might be that the action is designed to always run and we don't care about its status for the digest? However, the problem says to report CI status.

  Let's look at the data: the first line has a dash and then the description. In the other lines, we have "success" and "skipped". So the first one is missing the status. We'll assume it's not successful (or unknown) and flag it as an action item if necessary.

  However, note that the digest run is the one that produces this report, so if it failed, we wouldn't have the report? But we are generating the report now. So it's likely that the digest run is a separate action that runs after the fact? And it might have failed? But we don't have enough.

  Given the constraints, we'll report the CI status as:

  • AI Issue Review: success
  • Enhancement Guide: skipped
  • Daily Project Digest: (status not provided in the data, so we cannot confirm success)

  But note: the problem says "CI Status (latest runs on main)" and we are given three runs. We'll list them as:

  • Daily Project Digest: unknown (no status indicated)
  • AI Issue Review: success
  • Enhancement Guide: skipped

Dependency Changes (last 5 commits)

• None

Now, let's structure the digest:

Highlights (1-3 bullet points)

We need to pick the most important changes. Looking at the commits:

• The release of v0.14.0 (changelog commit) is a highlight because it includes multiple features: JavaScript actions, clickable containers, XPath fixes.
• The fix for widgets in bundled .mpk (issue Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) #679) is important because it addresses a limitation in widget authoring.
• The JavaScript actions feature (CREATE/DROP) is a major new feature.

So highlights:

• Released v0.14.0 with JavaScript actions, clickable containers, and XPath fixes.
• Fixed widget registration in bundled .mpk packages (issue Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) #679).
• Added support for CREATE/DROP JAVASCRIPT ACTION for both Mendix engines.

Code Changes (summarize by theme)

We already grouped the commits by theme above. We'll summarize:

• Widgets: Fixed registration of all widgets in bundled .mpk files (resolves Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) #679).
• Documentation: Updated changelog for v0.14.0 and added JavaScript actions user guide.
• Pages:
  • Preserved qualified enum literals in conditional Visible/Editable expressions (fixes regression Regression (v0.13.0): enum literal in conditional Visible/Editable expression mangled to a string → CE0117 #677).
  • Added support for clickable CONTAINER OnClick action (issue The click property on the Container is not supported by the MDL parser #603).
• XPath:
  • Fixed quoting of bare [%token%] inside bracketed constraints (issue XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply #641).
  • Added check to flag System.owner XPath references on entities without owner stored (issue XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply #641).
• Check: Renumbered widget rules for issue Datasource-typed pluggable-widget property passes 'check' but is silently dropped at 'exec' (CE0642) #643 to MDL-WIDGET05/06.
• JavaScript Actions: Implemented CREATE and DROP JAVASCRIPT ACTION commands for both Java and JavaScript engines.

Pull Requests

• Merged: None in the last 24h.
• Opened: None in the last 24h.
• Pending review: 2 open PRs (fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592 and docs: add manual test case documentation for all MDL command areas #386).

Issues

• New (last 24h): 3 issues (CREATE JAVA ACTION cannot create Enumeration parameter — serialized as entity ref, build fails ('selected entity no longer exists') #680, Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) #679, Regression (v0.13.0): enum literal in conditional Visible/Editable expression mangled to a string → CE0117 #677).

• Closed (last 24h): 2 issues (Daily Digest: 2026-06-21 #678, XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply #641).

• Total open: The repository stats say 1 open issue, but note: we have 3 new issues opened and 2 closed in the last 24h. However, the total open issues is given as 1 in the repo stats. This seems inconsistent.

  Let's check:

  • The repo stats say "Open issues: 1".
  • But we see 3 new issues opened and 2 closed in the last 24h.

  This implies that before the last 24h, there were some open issues, and then we opened 3 and closed 2, so net change: +1. Therefore, if the total open is now 1, then before the last 24h there must have been 0 open issues? But then after opening 3 and closing 2, we would have 1 open.

  However, note that the closed issues include Daily Digest: 2026-06-21 #678 (which is the daily digest for yesterday) and XPath constraint containing a [%…%] token (e.g. [%CurrentUser%]) fails CE0161 after apply #641 (an XPath issue). The new issues are CREATE JAVA ACTION cannot create Enumeration parameter — serialized as entity ref, build fails ('selected entity no longer exists') #680, Chart widgets not authorable via mxcli MDL (bundled .mpk only registers first widget; series datasource; AreaChart CE0463) #679, Regression (v0.13.0): enum literal in conditional Visible/Editable expression mangled to a string → CE0117 #677.

  So the total open issues now should be:
  (previous open) + 3 (new) - 2 (closed) = 1
  => previous open = 1 - 3 + 2 = 0.

  So it's consistent: there were 0 open issues before, then we opened 3 and closed 2, leaving 1 open.

  But wait: the repo stats say "Open issues: 1", which matches the current state.

  Therefore, we report:

  • New issues: 3
  • Closed issues: 2
  • Total open issues: 1

Repository Health

• Stars: 94
• Forks: 31
• CI Status:
  • Daily Project Digest: (status not indicated in the data) -> we'll note it as not successful? But since we don't have a symbol, we'll say "unknown" or check the context?
    However, in the data provided, the first CI run has no status symbol (just a dash) while the others have "success" and "skipped".
    We'll report:
    • Daily Project Digest: unknown (no status provided)
    • AI Issue Review: success
    • Enhancement Guide: skipped

Action Items

We need to look for anything that needs attention:

• Failing CI: The Daily Project Digest run does not show a success status. Since it's the digest run, and we are generating the digest now, it might be that the action failed? But note: the digest run is scheduled to run after the day? We don't know. However, if it's not marked as success, we should check.
• Stale PRs: We have two open PRs: fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592 (opened? we don't have the date, but it's been open for a while) and docs: add manual test case documentation for all MDL command areas #386 (which is from @retran and likely old). We don't have the exact dates, but since they are still open and no activity in the last 24h (no new PRs opened and none merged), they might be stale. However, without more context, we can only note that there are 2 open PRs that have not been merged recently.

---

Daily digest generated automatically — workflow source