Release v0.6.0 · PADAS/earthranger-cli

Highlights

Importing and previewing events (requests from @arky in #20, #21, #19)

events post --dry-run. Validates every event against its type's schema exactly as a real post does, prints one would post line per event, and sends nothing. With --no-validate it never connects, so a file can be previewed offline. (#42)
events post --file history.csv. A CSV is read directly, one event per row, with no YAML conversion step. event_type, time, title and lat/lon (or a location column holding lat,lon) are recognised case-insensitively; every other column is a detail field. Cell values are coerced conservatively: integers, decimals and true/false become numbers and booleans, everything else stays text, so dates, times, ids with leading zeros and codes like NO survive. --event-type is the default for rows without one; --map KEY=COLUMN points a field (or a reserved slot) at a differently named column. The delimiter is detected from the header (comma, semicolon, tab, pipe); errors name the file's line number; a row with surplus cells, a duplicate header, a column mapped twice, or both a location and lat/lon is refused before anything is sent. Rows get the same validation and --dry-run as a YAML batch. (#46)
events pull CATEGORY --event-type VALUE. A spec for just the requested types (repeatable) that keeps the category block and only the choice sets those types reference, so it applies directly; an unknown value lists the category's types. (#43)

Project

Every pull request and push to main now runs the suite and the linters on Python 3.11, 3.12 and 3.13; the release workflow builds on the 3.11 floor instead of whatever Python the runner had. (#45)
CONTRIBUTING.md records the process adopted after the 0.5.0 review rounds and what CI runs. (#37, #45)
The PyPI summary, keywords and links describe the whole tool. (#41, shipped in 0.5.1)

Full Changelog: v0.5.1...v0.6.0