Repository navigation
v0.1.40-alpha
Pre-releasev0.1.40-alpha — Google Calendar edits now reach Google
Phase 2, task 5. Everything built in tasks 1-4 has been inert until now:
the outbound sweep required a writable calendar and none existed. This
unlocks Google-synced calendars, and edits start pushing.
What a household can now do: create, edit and delete whole events on a
Google calendar in Basis, and see them in Google within about five minutes.
Changes made in Google still arrive on the hourly pull.
What it still refuses, deliberately: editing or deleting a SINGLE occurrence
of a repeating series. That is not an oversight — deleting one occurrence
adds an EXDATE to the master row, and pushing that would replace Google's
whole recurrence array and wipe exclusions it held, silently and
permanently. The spec always deferred per-occurrence editing to v2; what
went unnoticed until now is that EXDATE-on-master IS per-occurrence editing.
Basis says so at the point of action rather than accepting an edit it cannot
deliver.
Connecting a Google calendar now reads its actual access role and stays
read-only unless the household owns it or has writer access — a shared,
holiday or school calendar connects pull-only instead of failing every push
forever. ICS import into a synced calendar is refused, since it would stamp
ICS UIDs into the column that tracks Google's own event ids.
Outlook is unchanged: still pull-only, still read-only, no outbound path.
Known limitation: migration 0019 unlocks existing Google calendars without
being able to check access role — a migration cannot call the Google API. A
reader-only calendar connected before this release should be disconnected
and reconnected.
Install
curl -fL https://github.com/Springdale-Robotics/basis/releases/download/v0.1.40-alpha/basis-0.1.40-alpha.tar.gz | tar -xz
sudo bash basis-0.1.40-alpha/backend/deploy/native/install.sh --source basis-0.1.40-alphaBasis installs natively (Node/Postgres/Redis + systemd); there
is no Docker image. Local development still uses Docker for
Postgres/Redis/Ollama via backend/docker-compose.dev.yml.