From ab4175a89aa2e3f08b7b083b84d92cf2c15fed7e Mon Sep 17 00:00:00 2001 From: Padreug Date: Sun, 27 Sep 2026 23:12:12 +0200 Subject: [PATCH] chore(release): v1.6.1-aio.18 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - #62 `tickets_available` is always published, including zero. Omitting it used to mean "unlimited", which nothing else agreed with: api_get_event and api_ticket_create both read `amount_tickets < 1` as sold out, so a zero-capacity event advertised unlimited tickets on the card and returned 410 to every purchase. Three such events were live on aio-demo. The admin form no longer offers 0 either. No schema change. Existing zero-capacity events are not migrated — we cannot infer whether the organiser meant unlimited or forgot to set a number — and they will read as sold out once republished. The #55 sweep will not flag them on its own, so /republish-all is the way to refresh. --- config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.json b/config.json index 0b27bc8..6936bf6 100644 --- a/config.json +++ b/config.json @@ -1,6 +1,6 @@ { "id": "events", - "version": "1.6.1-aio.17", + "version": "1.6.1-aio.18", "name": "Events", "repo": "https://git.atitlan.io/aiolabs/events", "short_description": "Sell and register event tickets",