Skip to content

feat: announce new versions and give projects the agent rules on connect - #50

Merged
silships merged 1 commit into
mainfrom
feat/update-notice
Sep 25, 2026
Merged

silships merged 1 commit into
mainfrom
feat/update-notice

Conversation

@silships

Copy link
Copy Markdown
Owner

What changes

Update hint
Once a day figma-cli checks npm in a detached process and prints one line on stderr when a newer version exists:

figma-cli 2.3.0 is available (you have 2.2.1). Update: npm install -g figma-ds-cli@latest

The command never waits for the network and stdout stays clean. An AI agent that sees the hint can run the update itself. FIGMA_CLI_NO_UPDATE_CHECK=1 turns it off. CI and test runs skip it.

Agent rules without init-agent
figma-cli connect now writes AGENTS.md into a project folder that has none yet, so Claude Code and Cursor know the commands right away. A project is a folder with .git or package.json or CLAUDE.md or .cursor. It never writes into the home folder or anywhere else. An AGENTS.md that is not from figma-cli stays untouched.

Release 2.2.1.

🤖 Generated with Claude Code

- once a day figma-cli checks npm in a detached process and prints a one-line update hint on stderr
- connect writes AGENTS.md into a project folder that has none and still refreshes outdated copies
- release 2.2.1

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@silships
silships merged commit 6de4c8b into main Sep 25, 2026
3 checks passed
@silships
silships deleted the feat/update-notice branch September 25, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant