← Commit history

Publish 0.8.8

John Lauer ·6b7181b825 ·3mo ago ·parent 10e80e4
4 files changed +9−7
SKILL.md+6−4
@@ -203,10 +203,12 @@ each account authorizes independently: `adom-google --account personal auth`. (clean, no prefix). For an **attributed bot post** to a team space (deploys/alerts as "Kel (on behalf of john)"), use **[adom-gchat](/adom/adom-gchat)**, the post-only webhook bot. Rule of thumb: posting *as yourself* ⇒ `adom-google chat`; an *attributed bot announcement* ⇒-`adom-gchat`. Chat scopes ship in both modes (safe: `chat.messages` + `chat.spaces.readonly` +-`chat.spaces.create`; full: `chat.messages` + `chat.spaces`, which adds space creation and-metadata updates), so this works out of the box once authorized — tokens issued before v0.8.5-need a re-auth to pick up space creation (`adom-google scopes --require chat.spaces --auto-widen`).+`adom-gchat`. Chat scopes ship in both modes. **safe**: `chat.messages`, `chat.spaces.readonly`,+`chat.spaces.create` (create-only, no delete, no membership changes). **full**: adds `chat.spaces`+(create + metadata), `chat.memberships`, `chat.delete`, `chat.customemojis`, and the+`chat.users.*` family (read state, space settings, presence, sections). `chat.admin.*` is never+requested at any tier. Tokens issued before v0.8.8 need one re-auth to pick the new ones up:+`adom-google scopes --require chat.memberships --auto-widen`.  We use Google Contacts to store **service identities** (portal/account metadata for an API vendor), e.g. the JPMorgan Payments developer portal. Keep secrets (client secrets, portal
VERSION+1−1
@@ -1 +1 @@-0.8.7+0.8.8
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-google",-  "version": "0.8.7",+  "version": "0.8.8",   "type": "app",   "license": "MIT",   "description": "Drive your whole Google Workspace from the terminal \u2014 Gmail, Contacts, Drive, Sheets, Docs, Slides, Calendar, Tasks, Google Chat, plus a generic `api` passthrough to hit ANY Google API. Connect a personal @gmail (or another org's Google account) with ZERO setup via Adom's hosted Connector (`adom-google connect-personal`), or bring your own token-broker gateway (`provider set`) \u2014 Adom staff use the private adom-google-adom provider. One-click OAuth, no client secret on your machine.",
page.json+1−1
@@ -4,7 +4,7 @@   "slug": "adom-google",   "title": "Adom Google",   "brief": "Drive your whole Google Workspace from the terminal — Gmail, Drive, Sheets, Docs, Slides, Calendar, Tasks, Chat + any Google API.",-  "version": "0.8.7",+  "version": "0.8.8",   "visibility": "public",   "install": {     "binary_name": "adom-google"