Skip to content

v2.8.2

Choose a tag to compare

View all tags
@BattermanZ BattermanZ released this 14 Oct 11:27
· 31 commits to main since this release
v2.8.2
df15d24
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A fixes release with nothing new to learn. The headline is comments: the %% and <!-- --> remarks you leave in a note stop appearing on the rendered page, which on a read-only or demo Vault is the only page visitors ever see. Agents' attachment links get tightened in three places, What's new stops skipping releases, and Settings stops calling an on setting Off.

Note

Nothing needs action before you upgrade. No route, tool or environment variable changed meaning. One response did change shape: GET /api/settings now sends every on/off value as true or false, whatever .env says. Hiding comments is a display rule only, so the text stays in the file, search still finds it and agents still read it. Don't keep anything in a comment that people who can read the note must not see.

Fixed

Notes, Help and Settings

  • Comments in a note showed on the rendered page. Text between %% marks, which Obsidian shows only while you edit, and HTML comments <!-- --> both printed in full, and a read-only or demo Vault always opens on that page. The rendered page, the editor's preview, Help and search snippets now leave them out, and a heading inside a comment stays out of the table of contents. The live editor still shows them, so you can edit them. #573
  • An embedded note, ![[Other note]], drew as a broken image. It shows as a link to that note now. The Supported Markdown reference also gained a list of the Obsidian syntax Hatchdoor does not handle. #573
  • What's new skipped releases. If the server went from 2.8.0 to 2.9.0 to 2.10.0 while a browser stayed away, the pop-up listed 2.10.0 alone and marked it read, so 2.9.0's highlights, Action needed items included, never showed. It lists every release since that browser last looked now. Its Full changelog button also opens again on an instance with no web token. #582
  • Settings showed an on setting as Off. A value set in .env as 1, yes, on or TRUE turned the setting on but read Off, so HATCHDOOR_USAGE_REPORT_ENABLED=1 showed Off right above the install ID it had just created. #581

Transfer links

  • A link for a path spelled with ./ never worked. get_attachment and create_upload_link accepted ./Media/a shot.png, but the link kept the ./, curl strips it before sending, and Hatchdoor refused the link and told the agent to ask for a new one that failed the same way. Links carry the path without . segments or doubled slashes now. #586
  • A link could outlive a token change. A tool call that arrived just before the MCP token changed and finished just after got a link the new token accepted. Links are signed with the token the call came in on now, so changing the token strands every one. #587 GHSA-g9gj-9g32-8ffw
  • A detailed enough RUST_LOG wrote links to the log. Hatchdoor kept the MCP library's message logging quiet by naming three of its modules, so a RUST_LOG that named a deeper one, such as rmcp::transport::streamable_http_server::tower=trace, logged tool results with their links in them. Nothing the library logs below info gets through now, whatever RUST_LOG says. #587 GHSA-g9gj-9g32-8ffw

Agent install

  • An installing agent could stop reading the deploy page before its last step. The page is about 35 KB, and in a test install the agent printed the first 30,000 bytes, never came back for the rest, and so missed the step that shows you the web token. The agent part of the page now opens by telling it to save the page with curl and read the file to the end. #529
Assets 2
Loading