Prepare @vrtmrz/obsidian-plugin-kit 0.1.4

[vrtmrz]

Prepare @vrtmrz/obsidian-plugin-kit 0.1.4 as a compatible patch release, preserving the public API while removing keyed Notice dependence on newer host element properties.

Proposed release notes

@vrtmrz/obsidian-plugin-kit 0.1.4

24 August 2026

Fixed

• KeyedNoticeManager no longer relies on Notice.messageEl or deprecated Notice.noticeEl. It retains its own message root, making the manager usable with Obsidian hosts which do not expose those elements.
• Updating a keyed Notice after the user dismisses it now creates a fresh Notice instead of reviving the acknowledged instance during Obsidian's hide transition.
• Key reuse, expiry restart, lifecycle cleanup, and support for string and DocumentFragment messages retain their existing behaviour.

Compatibility

• This release does not change the public API.
• The package-wide obsidian >=1.8.7 peer dependency remains unchanged. Compatibility with older hosts is scoped to KeyedNoticeManager and does not declare package-wide support for Obsidian 1.7.x.

Validation

• Added 21 focused Notice tests, including a legacy-compatible Notice implementation without host element properties.
• Verified dismissal and fresh-Notice creation in Obsidian 1.13.6.
• Passed the complete workspace checks, tests, builds, package inspection, and packed-consumer validation.

Version choice and scope

This is a patch release from 0.1.3 because it fixes compatible behaviour without adding or changing a public contract. Only @vrtmrz/obsidian-plugin-kit is selected: @vrtmrz/ui-interactions remains at 0.1.2, and the package-wide Obsidian peer requirement remains unchanged.

The release preparation changes only the selected package manifest and its root lockfile entry from 0.1.3 to 0.1.4.

Verification

• npm ci
• npm audit --omit=dev --json: no production dependency vulnerabilities
• git diff --check
• NODE_OPTIONS=--max-old-space-size=3072 npm run verify:workspace
  • all workspace type checks, release-tool tests, package tests, builds, dry-run packs, and packed-consumer checks passed
  • @vrtmrz/obsidian-plugin-kit: 72 tests passed
  • release tools: 37 tests passed
  • octagonal-wheels: 972 Vitest tests and four Node tests passed
• NODE_OPTIONS=--max-old-space-size=3072 npm run test:e2e:obsidian:validated
  • the complete validated suite passed against reviewed Obsidian 1.13.6
  • the real keyed and grouped Notice scenarios passed
• Push CI for commit 7d13c6ca8716670fbea23134f0278008b1c6a4b9 passed all checks, tests, builds, and package inspection

Package inspection

The locally packed candidate contains 41 files and 43,034 bytes compressed. It contains the licence, README, documentation, compiled dist files and maps, and package metadata only.

• SHA-256: 197660583e13c5c52f721db6f25634c6806326d03dec4df037e8604b00a2dab4
• npm shasum: c88c9eb01a27274da1e6d111d80e4fd98dce0b27
• npm integrity: sha512-27Lb7Xl64yNzblLW67qOiSXMPJSngx6heAhyxDTsghMwNIgXRIJ8oo3FJbpqpA0IyS0mrAzQ6OVTJaIIE6DPtA==

The package is intended for public npm publication, initially under next. The protected staged workflow will rebuild the package from the exact merged main commit and record its own immutable checksum and provenance before publication.

Platform limits

Real-Obsidian validation was performed on Linux with Obsidian 1.13.6. This release makes no new Windows support claim and does not lower the package-wide Obsidian peer requirement.

Remaining release work

• Review and merge the exact release commit into main.
• Stage version 0.1.4 from the resulting exact main commit under next, and compare the workflow artefact with the reviewed candidate.
• Publish and validate the exact registry artefact, checksum, and provenance in a representative consuming plug-in.
• Promote the validated stable version to latest as a separate operation.