v0.3.3

S3-compatible storage providers and JSR source publishing

Summary

Quarry now supports S3-compatible storage providers (Cloudflare R2, MinIO) via custom endpoint and path-style addressing flags. JSR publishing switches to TypeScript source for better type preservation.

Highlights

• S3-compatible provider support — new --storage-endpoint and --storage-s3-path-style CLI flags enable Cloudflare R2, MinIO, and other S3-compatible backends
• JSR source publishing — SDK now publishes TypeScript source to JSR instead of compiled dist, preserving full type information
• Documentation updates — cli.md, configuration.md, and PUBLIC_API.md now cover R2/MinIO setup with examples and credential guidance

Upgrade Notes

• No breaking changes from v0.3.2
• New flags are additive; existing S3 and filesystem workflows are unchanged
• R2 users: set --storage-endpoint and --storage-s3-path-style with AWS credentials via environment variables

References

• #87 — S3-compatible provider support
• #88 — JSR source publishing fix
• #89 — Documentation updates
• #90 — Version bump

Full Changelog: v0.3.2...v0.3.3

What's Changed

• feat(lode): ✨ add S3-compatible provider support (R2, MinIO) by @justapithecus in #87
• fix(release): 🐛 publish TypeScript source to JSR instead of dist by @justapithecus in #88
• docs(lode): 📝 add S3-compatible provider docs to guides by @justapithecus in #89
• chore(release): 🔖 prepare v0.3.3 release by @justapithecus in #90
• docs(release): 📝 add changelog entries for v0.3.1–v0.3.3 by @justapithecus in #91

Full Changelog: v0.3.2...v0.3.3