Release 1.1.3 — ship .htm support - #16
Merged
Merged
Conversation
smcllns
marked this pull request as ready for review
June 17, 2026 20:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Cut 1.1.3 so the already-merged
.htmsupport (commit 70b8afa) actually reaches installed plugins. The vault-installed build was 1.1.2, which only registers.html— hence.htmembeds failed with "could not be found".Changes
manifest.json,package.json,versions.json→ 1.1.3 (no code change;.htmlogic already on main)test/test.sh:npm run build→bun run build(npm is blocked on dev machine; test couldn't build)Verification (live Obsidian)
.htm routes to html-docs view✓ and.htm embed registered✓ (live smoke test)app.viewRegistry.getTypeByExtension('htm')→html-docs,embedRegistry.isExtensionRegistered('htm')→ trueNotes
obsidian-cli evalresponse-timeout that truncates blocks awaiting longsetTimeouts — a pre-existing harness limitation (proven: a bare 1200ms-awaited eval returns empty), not a regression. Not fixed here to keep the release tight; can address separately.1.1.3is pushed (perrelease.yml).bun.lockleft untracked (repo is npm-based; CI usesnpm ci).