Google Calendar in chat: move and cancel single events, no surprise Meet links
The Google Calendar connector got a round of fixes. Events Portail added to your calendar no longer come with a Google Meet link you never asked for, and the chat now gets the event's link back, so it can show you where the event landed. You can ask it to move, rename or cancel one specific event, and it changes only that one. Before, the only way to remove something was to clear a whole stretch of time, and that also caught events that merely overlapped it, like an all-day event or a meeting running into the hour. Clearing a range now removes only what fits inside it, and does it faster. When a busy week has more events than one answer can show, the chat says so instead of presenting the first 20 as everything. Replies in chat also start a little sooner when you're signed in, because Portail no longer checks your connected apps from scratch on every message.
596 words
Events created from chat no longer get an automatic Google Meet link.
Ask to move, rename or cancel one event and only that event changes.
Moving one event in a repeating series changes only that occurrence, and the chat says so.
Clearing a time range leaves alone events that only overlap it, such as all-day events.
On a busy week the chat tells you when there are more events than it listed.
Chat replies start a little sooner when you're signed in: your connected apps are checked once a minute, not on every message.
Portail v2.11.4 shipped on 2026-11-12 as a patch release focused on google calendar in chat: move and cancel single events, no surprise meet links. The Google Calendar connector got a round of fixes. Events Portail added to your calendar no longer come with a Google Meet link you never asked for, and the chat now gets the event's link back, so it can show you where the event landed. You can ask it to move, rename or cancel one specific event, and it changes only that one. Before, the only way to remove something was to clear a whole stretch of time, and that also caught events that merely overlapped it, like an all-day event or a meeting running into the hour. Clearing a range now removes only what fits inside it, and does it faster. When a busy week has more events than one answer can show, the chat says so instead of presenting the first 20 as everything. Replies in chat also start a little sooner when you're signed in, because Portail no longer checks your connected apps from scratch on every message. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: events created from chat no longer get an automatic google meet link, ask to move, rename or cancel one event and only that event changes, moving one event in a repeating series changes only that occurrence, and the chat says so, clearing a time range leaves alone events that only overlap it, such as all-day events, on a busy week the chat tells you when there are more events than it listed, and chat replies start a little sooner when you're signed in: your connected apps are checked once a minute, not on every message. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.11.4 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.