v0.2.2 - 2025-2-28

What's Changed

API

POST /processes/:processID/execution

• Execution mode now determined per OGC API - Processes Requirements 25/26: honors Prefer: respond-async header when process supports both modes, defaults to sync otherwise
• Returns Preference-Applied response header when async preference is honored

GET /admin/resources

• New endpoint to view resource utilization for local jobs (docker, subprocess) and queue status

GET /jobs/:jobID/metadata

• Added recoveryNotice object to metadata format

Features

• Added restart recovery for docker, subprocess, and AWS Batch jobs, including status reconciliation and log handling.
• Introduced lost job status and surfaced it in UI status indicators (job list, job logs, status table).
• Recovered jobs annotate metadata with a recovery notice and write best-effort metadata when some fields are missing.
• Resource pool can force-reserve resources for already-running recovered docker jobs.

Configuration

• New MAX_LOCAL_CPUS and MAX_LOCAL_MEMORY environment variables (or --max-local-cpus and --max-local-memory CLI flags) to set resource limits for local job scheduling
• Process definitions are validated against these limits at startup and when adding/updating processes via API
• Processes without explicit resource requirements use default values

Documentation

• Added sequence diagram for local scheduler
• Added Recovery section to DEV_GUIDE

Deploy

🐳 Docker/Container

# Pull the image
docker pull ghcr.io/Dewberry/sepex:0.2.2

v0.2.1 - 2025-12-03

What's Changed

API

• Version information is added in landing page.

Configuration

• Repository URL is now configurable via REPO_URL environment variable. This URL is used for version links and metadata context references.

Documentation

• Changelog updated to new format

Deploy

🐳 Docker/Container

# Pull the image
docker pull ghcr.io/Dewberry/sepex:0.2.1

v0.2.0 - 2025-12-02

0.2.0

API

GET /jobs/:jobID/logs

• In response body container_logs key is replaced by process_logs

PUT|POST /processes/:processID

• Request payload schema has changed (See Process YAML Schema changes below)

Process YAML Schema

• command is now a first class object and moved outside of container
• config object is added
• maxResources and envVars are moved under config object
• image moved under host
• container object removed
• host.type valid options are changed from local | aws-batch to docker | aws-batch | subprocess

Features

• subprocess type processes now can be executed through API. They must be registered like other processes and will be called using OS subprocess calls.

Documentation

• A CHANGELOG.md file is added in the repo.
• Process templates are provided for all three host types in ./process_templates folder
• Windows setup instructions are added in README.md

v0.1.0 - 2023-07-07

Initial Release