Repository navigation
v1.5.4
Boardstate 1.5.4 lets you install a pinned release straight from this repository on Hermes 0.23.0, with no --force and no security prompt.
Install this release
hermes plugins install 100yenadmin/boardstate-hermes-plugin --ref af6ee0dac8bca16a5807e894bf84883d43b70b29 --enableCommit: af6ee0dac8bca16a5807e894bf84883d43b70b29
If Boardstate is already installed (for example at an older catalog pin), run hermes plugins remove boardstate first. Your board stays in boardstate-state. Then run the line above. Start or restart hermes dashboard for the Board tab. In Hermes Desktop, enable Boardstate under Capabilities → Plugins, and restart the app after an update.
Fixed
- On Hermes 0.23.0, a pinned
owner/repoinstall of 1.5.3 scannedcaution. A terminal got "Install anyway? [y/N]", and Hermes Desktop, scripts and closed-stdin installs were refused. Two pieces of dependency text in the committed sidecar bundle caused it, and neither ever ran: the default Pipedream URL in@boardstate/broker's unused connector presets, and a comment in the MCP SDK's stdio client that mentionssudo. The build now tree-shakes the broker's unused preset table and drops that comment. The scan on Hermes 0.23.0 now reportssafe, with no HIGH or CRITICAL finding. - Connector behaviour is unchanged. Operators still author every connector, remote MCP URLs included, in
boardstate.connectors.json, and connector tools still need an operator grant.
Changed
- README: the install section shows the pinned form and the upgrade path, and the security scanner notes match the current scan.
- CI runs the Hermes v0.23.0 install scanner on every commit and fails on anything that would not scan
safe(test/install_scan.py,test/scan-hygiene.mjs).
Full notes: CHANGELOG.md