v0.5.0

Event-bus adapters for downstream run completion notifications

Summary

Quarry v0.5.0 ships built-in event-bus adapters so downstream systems can receive real-time notifications when extraction runs complete, without external plumbing or shell wrappers.

Highlights

• Webhook adapter: HTTP POST with configurable headers, retries, and timeout — --adapter webhook --adapter-url https://hooks.example.com
• Redis pub/sub adapter: JSON PUBLISH to a configurable channel — --adapter redis --adapter-url redis://localhost:6379
• New CLI flag: --adapter-channel for Redis pub/sub channel name (default: quarry:run_completed)
• YAML config support: Full adapter stanza (type, url, channel, headers, timeout, retries) in project config files
• Best-effort delivery: Adapter failures are logged to stderr but never fail the run — data is already durable in Lode before the adapter fires
• Contract updates: CONTRACT_INTEGRATION.md and CONTRACT_CLI.md updated with both adapter types and all flags

Known Limitations

• Delivery is best-effort with retries; if all retries exhaust, the notification is lost. An outbox pattern for at-least-once guarantees is planned for a future release.
• Temporal, NATS, and SNS adapters are planned but not yet available.

References

• CONTRACT_INTEGRATION.md — adapter boundary and delivery semantics
• Integration guide — usage examples for webhook and Redis
• Configuration guide — YAML adapter config

Full Changelog: v0.4.1...v0.5.0

What's Changed

• feat(adapter): ✨ add webhook event-bus adapter for downstream notifications by @justapithecus in #103
• feat(adapter): ✨ add Redis pub/sub adapter for run completion events by @justapithecus in #107
• chore(release): 🔖 prepare v0.5.0 release by @justapithecus in #108

Full Changelog: v0.4.1...v0.5.0