All versions since 2.2.0

2.2.0

Oct 9, 2026

API version: 10.2.0

File Action Templates and Cron Triggers in folders: ActionTemplate and CronTrigger take an optional folder on create, get move_to_folder() and a folder filter on their query helpers. Their HCOs expose folder_path, parent_folder_link and move_to_folder_action.
Folder contents list Action Templates and Cron Triggers in action_templates and action_triggers; FoldableItemType gains ACTION_TEMPLATE and ACTION_TRIGGER.
ActionTemplate.set_job_folder() sets the folder for Jobs created from the template; the template HCO exposes job_folder and set_job_folder_action.

An output DataSlot without a target folder files its WorkData into the Job’s folder instead of the owner’s root (JMA #202); "/" is an explicit root target. Docstrings of set_output_folder and OutputDataSlotSetFolderAction describe the new default.

Oct 14, 2026

API version: 10.4.0

ActionTemplate.set_job_folder() accepts date placeholders such as {{date+1@Europe/Berlin}}, filled in when a Job is created from the template (UTC by default).
Models for the JMA statistics (API 10.3.0).

Oct 14, 2026

API version: 10.5.0

JobHco.scheduled_at: the UTC time a Job moved from ReadyForProcessing to Pending. It is None until the Job is scheduled, and for Jobs scheduled before JMA 2.7.0 that never started.

Oct 15, 2026

API version: 11.0.1

Models for the statistics of JMA API 11: StatisticsRootHtoOpenApi, the windows uploaded_from and processing_steps_from in StatisticsQueryParameters, and in StatisticsHtoOpenApiProperties the windows a result covers plus work_data_per_user, work_data_per_kind, upload_days, processing_steps and the new per-day fields of CompletionDayHto (compute_ms, time_to_start_p50_ms, time_to_start_p90_ms, produced_bytes).

Generated from JMA API 11.0.1 (JMA 2.8.1): enter_jma() against JMA 2.8 no longer warns about an API version mismatch.

Oct 17, 2026

API version: 11.0.1

set_tags and uploads with tags= accept tag values that are not ISO 8601 timestamps, such as Version=1.7.0, against JMA 2.8.2 and later. Earlier JMA versions read such a value as a date (1.7.0 as 2000-01-07) and rejected it with 400 “Detected timestamp without defining time zone”. The fix is in JMA; this package is unchanged apart from integration tests for it.

Oct 19, 2026

API version: 11.1.0

ProcessingStep.configure_deployment() takes resources=ResourcesConfiguration(cpu_millicores=..., memory_mi_b=..., disk_gi_b=...) as an alternative to resource_preset=. Pass exactly one of the two, otherwise the call raises ApiException; so do values that are not greater than zero or exceed the platform’s resource ceiling. resource_preset= keeps working as before and now stands for fixed values: xsmall 250/512/3, small 500/1024/5, medium 1000/4096/10, large 3000/14336/70, xlarge 6000/28672/200, xxlarge 14000/60416/300 (millicores/MiB/GiB). The deployment of a ProcessingStep (processing_step_hco.deployment) shows cpu_millicores, memory_mi_b and disk_gi_b; resource_preset is set only when the values are exactly those of a preset. Needs JMA API 11.1.

Oct 19, 2026

API version: 11.1.0

Published to PyPI. 2.6.0 reached only the internal package feed: its release pipeline failed before the PyPI upload. 2.6.1 contains the same code, so its changes are those listed under 2.6.0 below; use 2.6.1 instead of 2.6.0.