feat(plugin): show bundled release notes after an update

[Leo310]

What

Users now see the release notes after updating. The layout follows Obsidian's own release notes. CHANGELOG.md becomes the single source for them and is backfilled from the 2.0.0–2.2.0 GitHub release bodies (dates added, inner ## headings demoted to ###).

• "What's new" tab: opens in the main area, with the S2B wordmark, "What's new in X", "Released on DATE", and the latest release's notes in full. Below that, "Earlier releases" lists older versions as collapsible sections with their dates. #123 references become GitHub links; code spans and fenced blocks are left alone. There is also a link to all releases on GitHub.
• After an update: a notice says "Smart Second Brain updated to X · See what's new" and opens the tab. Every version newer than the stored lastSeenVersion is included, so releases a user skipped roll up and start expanded.
• Staying quiet: a fresh install records the running version and shows nothing. A pre-release build shows and records nothing, so a beta tester still gets the stable notes when the release lands. Data from before this feature announces only the running version.
• On demand: the "Show release notes" command and a Troubleshooting → Maintenance row open the tab with only the latest release expanded.
• Release workflow: the tag's ## X.Y.Z (YYYY-MM-DD) section is copied into the draft body, and a stable tag with no section fails before the build. A re-run of a stable draft rewrites its body from the changelog; a pre-release draft's hand-written body is left alone.
• SvelteItemView.mountComponent now unmounts any component it mounted earlier, so a view can re-render when setState arrives.
• Docs: AGENTS.md notes that the release section goes into CHANGELOG.md in the release commit, before tagging.

No network requests: the notes are bundled with ?raw (about 25 KB).

How I tested it

• Unit tests in test/utils/releaseNotes.test.ts cover:
  • changelog parsing, including the optional date
  • semver ordering, including pre-releases
  • the announcement rules: roll-up, unknown last-seen, beta, downgrade, a version without notes
  • linkifying, including skipping code
  • a check that the bundled CHANGELOG has a section for manifest.json's version
• Ran bun run check, format, lint and the full test suite; all pass.
• Checked live in the slot vault on desktop Obsidian 1.14:
  • On reload the update notice appeared (this vault's data predates the field, so it announced 2.2.0).
  • The command opens the tab with the logo, title, date, the latest notes, and collapsed earlier releases.
  • showReleaseNotes(3) expands the latest plus two earlier releases without duplicating the component.
  • dev:errors was clean.
• Not tried on mobile.
• The workflow's awk extraction was run locally against the backfilled file.

AI assistance: Claude Code wrote this from Leo's brief (bundled changelog shown on update, collapsed older releases, S2B logo, layout modelled on Obsidian's release notes). The tab, notice and workflow change still need Leo's review and live test.

Checklist

• bun run check, bun run format, bun run lint, and bun run test pass locally
• I tried the change in a real Obsidian vault (or explained above why that isn't applicable)
• I read CONTRIBUTING.md, including the section on AI assistance
• If this adds a provider, a bundled skill, a built-in tool, or changes manifest.json: I noted that the docs site needs updating (see "Documentation" in CONTRIBUTING.md) — n/a

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Adds release notes display and update announcement logic.

The PR appears safe to merge; no outstanding findings remain.

Summary

The PR bundles CHANGELOG.md to show release notes in an Obsidian tab, announces stable updates, and uses the same changelog sections for draft GitHub releases.

• Adds a command and settings entry for opening the notes on demand.
• Adds tests for parsing, version selection, and reference links.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A["CHANGELOG.md"] --> B["Bundled release-notes tab"]
  A --> C["Release workflow"]
  D["Stored last-seen version"] --> E["Update announcement"]
  B --> E
  C --> F["Draft GitHub release body"]

Loading

_{Reviews (5) · Last reviewed commit: "Merge remote-tracking branch 'origin/mai..."}