upgrade-mendix-version skillA
upgrade-mendix-version is agent-read markdown (skill) from mendixlabs/mxcli: Move a project to a newer Mendix version headlessly, with no Studio Pro. Use when raising a project's Mendix version, when a build complains the project version does not match MxBuild, or before adopting a newer runtime. Covers the one check that decides whether a converter must run, and the two green false successes that upgrade nothing..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Upgrading a Mendix version without Studio Pro
## Why this needs a skill
Both ways of getting it wrong **look like success**:
| what you do | what you see | what is true |
|---|---|---|
| `mxbuild --loose-version-check` | `BUILD SUCCEEDED` | the project is still on the old version |
| `UPDATE _MetaData SET _ProductVersion` | the project reports the new version, and mxcli agrees | every unit is read against the wrong schema |
Neither prints a warning. The first is not hypothetical — it is what happened to
the project that reported this, and it took going back to look at the version
column to notice that a successful build had upgraded nothing.
## The check that decides everything
A `.mpr` is SQLite. The version lives in one table, `_MetaData`, with columns
`_FormatVersion`, `_ProductVersion`, `_BuildVersion` and `_SchemaHash`.
Use Python rather than the `sqlite3` CLI: `python3` ships with a `sqlite3`
module, while the CLI is frequently absent (it is not in the mxcli devcontainer).
```bash
mprhash() { python3 -c "import sqlite3,sys
print(*sqlite3.connect(sys.argv[1]).execute(
'SELECT _ProductVersion,_SchemaHash FROM _MetaData').fetchone(), sep=' ')" "$1"; }
…Read the whole file at its exact version.
How to install
mdr add mendixlabs/mxcli/upgrade-mendix-version@git:20260831.70b0e5amdr add mendixlabs/mxcli/upgrade-mendix-version@sha256:38ab5b00f3978855Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pfzucldmno3hyvb6)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7502 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mendixlabs/mxcli · 124 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pfzucldmno3hyvb6 GET https://markdownregistry.com/api/v1/resolve?ref=mendixlabs/mxcli/upgrade-mendix-version GET https://markdownregistry.com/api/v1/blob/38ab5b00f3978855d2233974e81c840be5484ff68e485f190bf619f6f42fbb3d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.