1.0.0

What's Changed

New Features

• Add per-config subfolder slash literal toggle (#97)
  • New subfolderTreatSlashAsLiteral setting per config: when enabled, slash characters in subfolder field values are treated as literal (e.g. AC/DC → single folder AC-DC) instead of creating nested folders
  • Default is false, preserving legacy behavior where 2024/Q1 creates a two-level folder hierarchy
  • Toggle appears beneath every subfolder field picker across Airtable, SeaTable, and Supabase configurations
  • Existing settings migrate automatically with false fallback — no behavior change for current users
• Add isSubfolderSafe field filter and UI parity for subfolder dropdowns across all providers (#100)
  • New isSubfolderSafe / getSubfolderSafeTypes methods on FieldTypeMapper exclude attachment, link, and object-shaped column types (collaborator, geolocation, barcode, etc.) from subfolder field pickers — fixes over-restrictive filtering for Airtable and under-restrictive filtering for SeaTable / Supabase
  • Settings UI now surfaces stale stored subfolder/filename values that no longer match the active filter as a synthetic (unsupported / hidden) option, so users can re-select without silent data loss
  • Runtime guard in determineFolderPath falls back to flat layout when a field value resolves to [object Object], protecting legacy configs that predate this change

Maintenance

• Fix release workflow trigger + bump GitHub Actions to v6 + add repo templates (#99)
  • release.yml tag filter changed from "*" to "[0-9]*" to prevent sync tags from accidentally triggering the publish workflow
  • actions/checkout and actions/setup-node updated from v3/v4 → v6; Node.js bumped from 18 → 20 (active LTS) across all workflows
  • Added CODEOWNERS, pull_request_template.md, and issue templates (bug report, feature request)