marketplace update --to refuses without --force, citing local edits nobody made #1441

Environment

• mxcli: v0.26.0 (release binary, 2026-10-11)
• Mendix version: 10.24.0 (blank app from mxcli new R --version 10.24.0 --theme none --skip-init)
• OS: Linux x86_64 cloud container (no Studio Pro; mx/mxbuild only)
• Also seen on: Siemens FSM template (Marketplace) 9.24.2; 10.24 / 11.13.0 converted copies

Summary

marketplace update --to refuses with "N element(s) have been changed locally" on a module nobody edited. In the blank-app run the module had just been written by marketplace update itself, so the baseline comparison reports 44 of 50 elements as changed.

Reproduction

Blank 10.24.0 app (mxcli new R10 --version 10.24.0 --theme none --skip-init). It ships NanoflowCommons 6.0.0, which is no longer downloadable as a baseline, so first move to a published version:

$ mxcli marketplace update 109515 -p R10/R10.mpr --module NanoflowCommons --to 5.2.1 --no-baseline
...
NanoflowCommons updated 6.0.0 → 5.2.1
  58 units copied, 12 element identities preserved, 0 role grant(s) restored.

Without touching anything, ask for another published version:

$ mxcli marketplace diff 109515 -p R10/R10.mpr --to 5.2.0
NanoflowCommons — installed 5.2.1 (Mendix 10.24.0.73019)

  Locally modified (44 of 50 elements):
    changed   JAVASCRIPT_ACTION Base64Decode
    changed   JAVASCRIPT_ACTION Base64DecodeToImage
    ...
$ mxcli marketplace update 109515 -p R10/R10.mpr --to 5.2.0
refusing to update: 44 element(s) have been changed locally and the update would discard them:
    JAVASCRIPT_ACTION Base64Decode
    ...

The same 44 JavaScript actions (including Wait and Vibrate) are reported on the FSM template converted in place to 10.24 (mx convert -p -s .) with marketplace update 109515 -p fsm.mpr --to 5.2.1; the refusal ends with - Then update: --force.

Expected

No local edits reported for an unmodified module; the update proceeds without --force.

Actual

44 of 50 elements (all JavaScript actions) are reported as locally modified and the update is refused.

Impact

Every update needs --force, which also removes the guard that protects real edits; usability.