Repository navigation
1.0.8
npm 1.0.8 (all 14 @metaobjectsdev/* packages in lockstep), PyPI 1.0.8 and NuGet 1.0.8.
Maven Central has no product change and stays at 8.0.7 (convergent publishing). metamodelVersion
stays 1.0. Gated by 1.0.8-rc.1 on the adopter estate: rc-gate.sh 7/7, contract suite 43/43 in
all five ports.
Upgrading: nothing to regenerate. Generated output is unchanged; the fixes are in the C# and
Python CLIs (warnings, template-spec selection) and in the docs.
Fixed
- A generator selected without the generators its output references now warns, in C#
and Python. Python--generators entity,routes,namesemitted a router that imports
<entity>_filter_allowlist, so the package failed at import withModuleNotFoundError;
C#--generators entity,routesemitted handlers that referenceAppDbContextand
<Entity>FilterAllowlistand did not compile. Pythonroutesnow declares
entity, filter-allowlist. C# gains therequiresmechanism TypeScript and Python
already had:routesrequiresentity, db-context, filter-allowlist,db-context
requiresentity, and the prompt-tier generators requireentity.genwarns and
--listshows(requires: ...). Advisory, as before: a hand-written file at that path
is allowed. - A template spec alone is a generator selection, in C# and Python.
genrefused a
project that generates only through atemplate-spec.json("no generators selected"),
so the documentedgen --template-rootexamples failed as printed. C#verify --codegenreturned clean for the same project without checking anything. Both now
resolve the spec before deciding nothing was selected. C#genalso reports an empty
selection as a usage error (exit 2) instead of "metadata did not load cleanly". - The Python and C# port pages' first
genexamples named no generators, so, codegen
being opt-in, they wrote nothing, and the Pythonverifybeside it checked nothing and
exited 0. Both now name the suite. The Python page also shows the template file its render
example reads and how to serve the generated router.
Changed
- Docs: generated code has "no proprietary runtime", not "no MetaObjects dependency".
Entity and model code imports nothing from MetaObjects at runtime; the REST, prompt,
client and runtime tiers import ordinary Apache-2.0 packages. The shipped codegen skill
said otherwise, so the agent-context an adopter installs changes. - ADR-0034: runtime metadata access is core; its HTTP adapters are helpers.
runtime-ts's root and./drivers(ObjectManagerand the layer under it) are core;
./fastify,./honoand./drizzle-fastifyare reference helpers. No code change.