v0.4.1

YAML config file support and config hardening

Summary

v0.4.1 adds a --config flag to quarry run that loads project-level defaults from a YAML file, reducing CLI flag repetition across invocations. Includes environment variable expansion, inline proxy pool definitions, and strict unknown-key rejection.

Highlights

• --config quarry.yaml — YAML project-level defaults for quarry run
• ${VAR} and ${VAR:-default} environment variable expansion in config files
• Inline proxies: key replaces deprecated --proxy-config JSON file
• KnownFields(true) rejects unknown YAML keys to catch typos early
• --source, --storage-backend, --storage-path no longer required on CLI when provided via config
• Hardened config edge cases: env expansion boundaries, whitespace-only YAML, Duration validation, retries nil vs zero

Upgrade Notes

• SDK and CLI must both be at v0.4.1 (lockstep versioning)
• No breaking changes to existing APIs
• --proxy-config still works but emits a deprecation warning — migrate to proxies: in YAML config

References

• Configuration Guide
• PUBLIC_API.md — Config section
• CONTRACT_CLI.md

Full Changelog: v0.4.0...v0.4.1

What's Changed

• feat(config): ✨ add --config flag for YAML project-level defaults by @justapithecus in #104
• chore(release): 🔖 prepare v0.4.1 release by @justapithecus in #105
• chore(docs): ✏️ fix missed v0.4.0 version references by @justapithecus in #106

Full Changelog: v0.4.0...v0.4.1