Skip to content

v1.3.0

Latest
Latest

Choose a tag to compare

View all tags
@carolinevrauwdeunt-lab carolinevrauwdeunt-lab released this 11 Nov 12:54
v1.3.0
cdc59b9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Approve proposals from your phone: every new proposal can now also come to you as a Slack message, with Approve and Dismiss. The room keeps running on your computer, and nothing on it is opened to the internet.

New: approving from Slack

  • A message per proposal. The Exec Room's Slack app sends you a direct message for each new card: what kind it is, who proposed it, the room and chat, the summary and where it goes (the maker, the repo, the Notion database, the email recipients, the file). Drafts, briefs, issue text and email text stay in the room.
  • Approve or Dismiss with a tap. A tap does exactly what the card's button does, with the same checks. Sending a proposal back for a revision needs a note, so that stays in the room. Approving an email draft records the decision; you send it from the room, as always.
  • Only you decide. Only taps from the Slack member set as the approver count; anyone else's tap does nothing.
  • The message keeps up. After a decision, in Slack or in the room, the message shows what happened (done with a link, failed with the reason, or dismissed) and the buttons go. An open room page picks up a decision made in Slack by itself, and the card and the Decisions list say "in Slack".
  • Nothing listens on your computer. The room connects out to Slack (Slack's Socket Mode) and taps come in over that connection.
  • Off until you set it up. About 10 minutes: create the Slack app from docs/slack-app-manifest.json, put its two tokens in 1Password, and add a slack block to room.config.json. The README's Approving from Slack has the steps, including how to reuse a Slack app you already have. If a token can't be read or a setting is wrong, the room starts without Slack and says why, in the terminal and on the page.

Changed: Node.js 22 or newer

The Exec Room now needs Node.js 22+. Node 20 no longer gets security updates, and approving from Slack uses the WebSocket that Node 22 has built in. setup.sh checks for it, and the tests run on Node 22 and 24. On an older Node, the room says that Slack needs Node 22.

Updating

  1. Check your Node version with node --version. If it starts with v20 or lower, install Node 22 or newer first.
  2. Pull the new version and restart the room.

Nothing changes until you add the slack block: without it, the room works as before.

Assets 2
Loading