Daily Digest: 2026-05-12

[github-actions]

We are given a daily digest for 2026-05-12. 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 (as of the digest date):

• Stars: 80
• Forks: 27
• Watchers: 7
• Open issues: 1 (but note: we have issues opened and closed in the last 24h, so we'll compute the current open issues from the data)

Commits (last 24h): 20 commits by Andrej Koelewijn.

Pull Requests:

• Merged: none in last 24h
• Opened: none in last 24h
• Currently Open PRs: one (docs: add manual test case documentation for all MDL command areas #386)

Issues:

• Opened (last 24h): three (Generate Page: I need to update the DataGrid 2 widget by right-clicking it and selecting 'Update widget' #549, CE0463 on engine-routed pluggable widgets (Accordion, Maps, PopupMenu, AreaChart) #548, Column-level CaptionParams / ContentParams / ShowContentAs dropped in datagrid_builder #547)
• Closed (last 24h): one (Daily Digest: 2026-05-11 #546)

CI Status (latest runs on main):

• Daily Project Digest: success (2026-05-12T09:30:25Z)
• Nightly Release & Integration Tests: failure (2026-05-12T05:56:09Z)
• Build, Test & Lint: success (2026-05-12T05:55:50Z)

Dependency Changes: none in last 5 commits.

Now, let's structure the digest:

1. Highlights

We need 1-3 bullet points of the most important changes.

Looking at the commits, we see:

• A lot of fixes related to CE0463 (combobox, placeholder IDs, etc.)
• Work on object-list for pluggable widgets (grammar, extraction, serialization)
• Fixes for nightly CI failures on Mendix 10.24
• Documentation updates

The most important might be:

• Progress on pluggable widget support (object-list keywords, extraction, serialization) which is a major feature.
• Fixes for CE0463 (a recurring issue) and other widget-related bugs.
• The nightly CI failure that needs attention.

But note: the digest is for a project that is actively working on Mendix 10.24 compatibility and pluggable widgets.

Let's pick:

• Significant progress on pluggable widget support: added object-list keywords, extraction to .def.json, and serialization of object-list child blocks.
• Multiple fixes for CE0463 (combobox and placeholder ID issues) and other widget bugs.
• Nightly CI failure on Mendix 10.24 integration tests that requires investigation.

2. Code Changes

Summarize commits by theme (not individually). We have 20 commits.

Themes observed:

• Pluggable Widget Support (Object-List):
  • Added object-list keywords for grammar (8b9c7c3)
  • Extract object-list properties to .def.json (753c346)
  • Serialize object-list child blocks to BSON (a8ee5cf)
  • Added test coverage for object-list extraction (377f23f)
  • Added aspirational fixture and v0.10.0 acceptance fixtures for pluggable widgets (483c6d8, 99a2957)
• CE0463 Fixes (combobox and placeholder ID issues):
  • Guard auto-populate and null selectAllButtonCaption for combobox (03a4f05)
  • Unique placeholder IDs for TextTemplate translations (8ead1cf)
  • Populate TextTemplate translation defaults + Editable=Always on filters (67102aa)
  • Add AllowUpload field to WidgetValueType BSON (dc02d4c) [closes one CE0463 gap]
• Grammar and Parsing Fixes:
  • Require not(expr) form in grammar (4019032) and document it (31d3ea5)
  • Add grammar as dependency of build, test, and release (fcbe04c)
• Widget-Specific Fixes:
  • Align datagrid WidgetObject boolean defaults (aea000b)
  • Add required CustomWidget envelope fields to filter widgets (301e329)
  • Reorder WidgetObject Properties to match WidgetType PropertyTypes order (365f6d1)
  • Two ALTER PAGE bugs (939f039)
• CI and Testing:
  • Repair three nightly CI failures on Mendix 10.10.24 (8e106b3)
  • Clean up v0.10 fixture loose ends (4069b60)
  • Go fmt all files (e8b2173)
• Documentation:
  • Document not(expr) parens requirement (31d3ea5)
  • Add placeholder-$ID-uniqueness gotcha (e90e700)
  • Widget BSON version compatibility + CE0463 methodology (a0f693a)

3. Pull Requests

• Merged (last 24h): None
• Opened (last 24h): None
• Pending review (currently open): One (docs: add manual test case documentation for all MDL command areas #386)

4. Issues

• New (last 24h): 3 (Generate Page: I need to update the DataGrid 2 widget by right-clicking it and selecting 'Update widget' #549, CE0463 on engine-routed pluggable widgets (Accordion, Maps, PopupMenu, AreaChart) #548, Column-level CaptionParams / ContentParams / ShowContentAs dropped in datagrid_builder #547)
• Closed (last 24h): 1 (Daily Digest: 2026-05-11 #546)
• Total open: We are told in the repository stats that open issues are 1, but note that we have 3 new and 1 closed in the last 24h. However, the repository stats provided at the top say "Open issues: 1". This might be the count at the time of the digest generation (before the last 24h activity). But the digest says "Open issues: 1" in the stats, and then we have 3 opened and 1 closed in the last 24h. So the current open issues would be: previous open (1) + 3 opened - 1 closed = 3. However, the repository stats section says "Open issues: 1", which is likely the count at the start of the period. We should use the provided stat for the total open? But note: the digest is for 2026-05-12, and the stats are given as of that day.

Looking at the provided data:

## Repository Stats
| Metric | Count |
|--------|-------|
| Stars | 80 |
| Forks | 27 |
| Watchers | 7 |
| Open issues | 1 |

This is the current state at the time of the digest. However, we then see:

• Issues Opened (last 24h): 3
• Issues Closed (last 24h): 1

This implies that the open issues count of 1 is before the last 24h activity. But the digest is generated after the last 24h activity? Actually, the digest is for the day 2026-05-12, and the stats are likely the current state at the time of writing the digest (which would include the last 24h). However, the way the data is presented, the stats are separate and then we have the last 24h activity.

To avoid confusion, we'll report:

• New issues (last 24h): 3
• Closed issues (last 24h): 1
• Total open issues: as per the repository stats provided (which is 1) but note that this might be outdated. However, the problem says to use the raw data provided. The raw data says "Open issues: 1" in the stats, and then we have the last 24h activity. Since the stats are given at the top, we'll use that for the total open.

But note: the digest is titled "Daily Project Digest: 2026-05-12", and the stats are part of the digest. So the stats are the current state as of the digest. Therefore, the open issues count of 1 is after the last 24h? But then we see 3 opened and 1 closed in the last 24h, which would change the count.

Alternatively, the stats might be the state at the beginning of the day, and the last 24h activity is the activity during the day. Then the current open issues would be: 1 (from stats) + 3 (opened) - 1 (closed) = 3.

However, the repository stats section says "Open issues: 1", and then we have a separate section for issues opened and closed in the last 24h. It is common in such digests to have the stats as the current state, and then the last 24h activity as changes. But if the stats are current, then the last 24h activity should not change the open issues count from the stats. This is confusing.

Let me re-read: the digest says "Repository Stats" and then lists Open issues: 1. Then later, under "Issues", we have "Issues Opened (last 24h)" and "Issues Closed (last 24h)". This suggests that the stats are the current state (at the time of the digest) and the last 24h activity is the change that led to that state? But then the numbers don't add up: if currently open issues are 1, and in the last 24h we opened 3 and closed 1, then the open issues 24h ago would have been: 1 - 3 + 1 = -1, which is impossible.

Therefore, the stats must be the state at the beginning of the period (or at a fixed time) and the last 24h activity is the change during the last 24 hours. Then the current open issues = stats open issues + opened - closed.

But the stats say "Open issues: 1", and we have 3 opened and 1 closed in the last 24h, so current open issues = 1 + 3 - 1 = 3.

However, the problem says: "Repository Stats" and then lists the metrics. It doesn't specify if it's current or at the start. But in the context of a daily digest, the stats are usually the current state. But then the last 24h activity should be reflected in the stats?

Given the confusion, I will follow the data as provided and note:

• The repository stats at the top say "Open issues: 1". We'll take that as the current total open issues (as of the digest time).
• Then, the issues opened and closed in the last 24h are additional details about the activity.

But note: the digest is for 2026-05-12, and the stats are provided at the top. The commits and activities are from the last 24h (which would be up to the time of the digest). So the stats should reflect the state after the last 24h activity.

However, the numbers don't add up. Therefore, I suspect the "Open issues: 1" in the stats is a mistake, or it is the count excluding some issues? Alternatively, the stats might be from a previous run.

But the problem says: "Generate a concise daily digest from the raw data provided." So we must use the raw data as given.

We have two options for the issues section:
Option 1 (as per the stats):
Total open issues: 1
New (last 24h): 3
Closed (last 24h): 1

Option 2 (calculating from the activity and assuming the stats are the starting point):
Total open issues: 1 (from stats) + 3 - 1 = 3
New (last 24h): 3
Closed (last 24h): 1

But note: the stats section says "Open issues: 1", and then we have a separate section for issues. The digest also has a section for "Issues Closed (last 24h)" which is 1. If the total open issues is 1, and we closed 1 in the last 24h, then we must have opened 0 to keep it at 1? But we opened 3.

This is inconsistent.

Looking at the raw data again: the repository stats are given in a table, and then we have sections for commits, PRs, issues, etc. The issues section says:

• Issues Opened (last 24h): 3
• Issues Closed (last 24h): 1

And the repository stats say open issues: 1.

I think the safest is to report the repository stats as the current state (so open issues = 1) and then note the activity (3 opened, 1 closed in the last 24h). But then we must note that the activity does not match the current state? Alternatively, the stats might be outdated.

However, in the context of the problem, we are to

---

Daily digest generated automatically — workflow source