@particle-academy/google-calendar-ui 0.4.1 → 0.4.2

package/CHANGELOG.md

@@ -8,6 +8,24 @@ The four packages share one version, because they are generated from one
 `provider/` definition and a version that meant something different in each
 would be a version nobody could reason about.
 
+## [0.4.2] — 2026-11-14
+
+### Added
+
+- **Complete setup steps**, in SETUP.md and the registry index. Every Google connector shares
+  the same first four, because they share one consent grant:
+  - the Cloud project;
+  - enabling the API;
+  - the consent screen (Branding, Audience with test users, Data Access with this
+    connector's scopes);
+  - a Web application OAuth client with `{{oauthRedirectUrl}}` as an authorized redirect URI.
+  - a random channel token per connection, and `{{webhookUrl}}` over HTTPS with a valid
+    certificate; channels are never renewed automatically;
+  - an AGENT step that connects an account and checks it works.
+
+  Each step cites the Google page it was checked against on 2026-11-14.
+- A one-line `summary`.
+
 ## [0.4.1] — 2026-11-08
 
 ### Fixed

package/README.md

@@ -33,6 +33,17 @@ dependencies nobody is tracking.
 
 Everything below is generated from `provider/manifest.json`, so it cannot disagree with what the packages do.
 
+### On Google Calendar's side
+
+1. **Create (or reuse) the Google Cloud project for **your app's name**** — Every Google connector shares ONE consent grant (oauth.grant "google"), so use one project and one OAuth client for all of them: one consent and one refresh token per person. ([developers.google.com](https://developers.google.com/workspace/guides/create-project))
+2. **Enable the Google Calendar API** — Console: APIs & Services, Library; open the Google Calendar API and click Enable. ([developers.google.com](https://developers.google.com/workspace/guides/enable-apis))
+3. **Configure the consent screen** — Console: Google Auth platform, Branding (app name **your app's name**, support email, contact email), then Audience: Internal for people inside your Google Workspace organisation only, or External (while it is in testing, add each tester under Test users). Then Data Access, Add or Remove Scopes, and add `https://www.googleapis.com/auth/calendar.events` beside the scopes of any other Google connector you use. You cannot remove the consent screen once it is configured. ([developers.google.com](https://developers.google.com/workspace/guides/configure-oauth-consent))
+4. **Create a Web application OAuth client** — Console: Google Auth platform, Clients, Create Client; type Web application. Under Authorized redirect URIs click Add URI and paste **your host's OAuth redirect URL**, then Create. Copy the client ID and client secret when the client is created. ([developers.google.com](https://developers.google.com/workspace/guides/create-credentials))
+5. **Give each connection a channel token, and serve **your host's webhook URL for this connector** over HTTPS** — events_changed opens a channel whose notifications go to **your host's webhook URL for this connector**, which must be HTTPS with a valid certificate (self-signed, untrusted, revoked or wrong-host certificates are refused). Google echoes the channel token in X-Goog-Channel-Token on every notification, so generate a random token per connection and never put an OAuth token in it. A channel is never renewed automatically: replace it with a new watch before it expires. ([developers.google.com](https://developers.google.com/workspace/calendar/api/guides/push))
+6. **Connect an account and check it works** — Connect one Google account through **your app's name**'s OAuth flow, then run the check below. ([developers.google.com](https://developers.google.com/workspace/calendar/api/guides/push))
+
+Every step in full — who does it, what to paste, which credentials it yields, and how you know it worked — is in [SETUP.md](SETUP.md).
+
 ### Credentials
 
 A Google Calendar connection holds 5 values.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@particle-academy/google-calendar-ui",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "Google Calendar's authoring surface for fancy-flow — the node kinds, their config schemas and their declared output shapes. React on every host; carries no executor.",
   "repository": {
     "type": "git",