v0.4.1

Calendar functions now declare separate path VARCHAR and content BLOB overloads instead of accepting ANY.

• Applies to ical_events, ical_todos, ical_calendar_name, ical_event_count, and is_valid_ical.
• Unsupported argument types now fail during SQL binding instead of being converted to file paths.
• Existing path, byte-content, malformed-feed, and NULL behavior is preserved.
• Function discovery includes precise argument types and descriptions for each overload.

Validation: 14 Java unit tests, SQL integration tests over stdio/HTTP/Unix sockets, and metadata linting with no findings.

Compatibility: Calls using VARCHAR paths or BLOB content keep working. Callers passing other types must supply a valid path or calendar bytes explicitly. Requires VGI protocol 3.3, as in v0.4.0.

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

v0.4.0

Full Changelog: v0.3.0...v0.4.0

v0.3.0

VGI protocol 3.2.

• deps: farm.query:vgi 0.46.0 -> 0.47.0 (protocol 3.2); vgirpc stays at 0.33.3
• metadata: shorter main schema title ("iCalendar Functions") and a new catalog vgi.subtitle, so the worker passes vgi-lint-check 2.2 (VGI147/VGI148) at 100/100

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Full Changelog: v0.1.0...v0.2.0

v0.1.0

What's Changed

• ci: multi-transport SQL E2E (subprocess + http + unix) by @rustyconover in #1

New Contributors

• @rustyconover made their first contribution in #1

Full Changelog: https://github.com/Query-farm/vgi-ical/commits/v0.1.0