Skip to content

v1.2.1

Latest

Choose a tag to compare

@mah0001 mah0001 released this 30 Jun 13:38

Summary

This patch release refines how the service handles filesystem paths. Paths supplied by the Metadata Editor are now consistently resolved to their canonical form and validated against STORAGE_PATH before use, aligning all file endpoints on a single validation approach introduced in 1.2.0.

Changes

  • Added a unified resolve_safe_path() helper that normalizes paths and enforces the STORAGE_PATH boundary
  • Updated CSV, geospatial, and core file endpoints to use the resolved canonical path for all filesystem access
  • No API or configuration changes