Repository navigation
[v0.109.0] - 2026-11-18
Fixed
- A model's answer that does not fit names the model and the concept:
model.output_schema_mismatchnow carries itsconceptparameter, the concept the step resolved for the run, a dynamic output's included, and itsmodelonPipeLLM's text path too, so the caller reads the registry's sentence naming both where it read the code's generic title.PipeLLM,PipeStructureandPipeJudgefill them, whether the failure reaches them wrapped or not. - A deeply nested template is the method's fault: a template nested past what Jinja2 can parse, walk or compile, such as a hundred nested parentheses, attribute reads, filters or
{% if %}blocks, is refused at load as a template that does not parse, and at render asmethod.template_invalidon a method's template, where it failed asruntime.unexpectedwith aRecursionError,SyntaxErrororIndentationError. Every template parse inpipelex.tools.jinja2goes through the newparse_jinja2_template, which refuses a tree deeper thanMAX_TEMPLATE_NESTING_DEPTHwithTemplateNestingError, aTemplateSyntaxError.
Security
pipelex-agent runnever revives classes from a run's result: rendering a result whosemain_stuff.jsonis a string decodes it as plain JSON, where it went throughkajson.loads, which imports the module and calls the class that a__module__and__class__pair names, so a hostile or self-hosted--base-urlcould start a process on the developer's machine. Only the date, datetime and time markers the local runner writes are read back, as ISO strings.pipelex build output --format pythonwrites every value as a literal (Breaking): a structure field's choice, or any other string, is written through Python's own escaping, so a choice holding quotes, parentheses, an equals sign or a line break stays a string in the generated example instead of being emitted as code.ConceptRepresentationGenerator.generate_field_valuereturns a nested class as aPythonClassCallnode in the Python format, where it returned the instantiation as a string.- A structure field's nested type name never becomes code in a generated module (Breaking): a list's
item_typeand a dict'svalue_typeare refused at load, asmethod.schema_violation, unless they name a field type (text,integer,number,boolean,date,datetime,time,list,dict,concept) orAny, where any other name loaded and projected asAny; a list of concepts isitem_type = "concept"with itsitem_concept_ref. A line break in such a name ended the# imprecise:comment thepython-pydanticandpython-structurestargets wrote and turned the rest of it into a statement ofmodels.pyorstructures.py, which ran when the module was imported: the comment now quotes the name withreprand leads every line with its own#, and every emitted Python module is parsed and refused withCodegenEmissionError,runtime.unexpected, when it holds any statement other than its imports and its classes of docstrings and fields. - The server refuses custom Python on the inline request shape too:
POST /v1/execute,/v1/startand/v1/validateanswer501 pipelex.deployment.custom_code_requires_sandboxto a.pyfile sent inresourcesbesidemthds_contentson a deployment that is not sandbox-hosted, and refuse one declaring a structure class with422 pipelex.deployment.python_structures_refusedon a sandbox-hosted one, as they already did forfiles,bundle_b64andmethod_ref.
What's Changed
- fix/Schema-mismatch-concept · L-261117-2cce8d by @lchoquel in #1571
- fix/Security-sweep-fixes · L-261117-e0a800 by @lchoquel in #1572
- fix/Codegen-comment-injection · L-261117-249187 by @lchoquel in #1573
- Release v0.109.0 by @lchoquel in #1574
Full Changelog: v0.108.0...v0.109.0