Skip to content

v1.3.0

Choose a tag to compare

View all tags
@mooja77 mooja77 released this 03 May 17:59
v1.3.0
57903d6

Three additive feature improvements. Every v1.2.4 flag, positional command, and progress.json file behaves unchanged — no migration required.

What's new

  • --wizard alias for --guided plus a wizard positional alias for setup (#13). Use whichever name feels more natural.
  • --reauth flag clears the saved Microsoft session (.access-token + msal-cache.json) and re-runs sign-in (#13). The most common 'something's wrong' state — expired token — is now one command instead of three.
  • ENML edge-case hardening (#12):
    • <en-codeblock language="X"> → <pre><code class="language-X">
    • Nested tables in <td> flattened to pipe-separated text (OneNote can't render them; v1.2.4 left them visually broken)
    • Footnote refs → <sup>[N]</sup>; back-links stripped; <section.footnotes> → <div.endnotes>
    • <en-media> style/width/height preserved on <img>/<object> (v1.2.4 dropped them)
    • <en-crypt> placeholder reworded with actionable guidance
    • Unknown <en-*> elements emit [unsupported: en-foo] markers instead of silent pass-through
  • Resume primitives for OneDrive chunked uploads (#14): markAttachmentInProgress / getActiveUploadSession / markAttachmentCompleted helpers in progress.js. Schema bump is purely additive (new optional inProgressUploads: {} field; version stays at 2). The actual >25MB upload-session integration in onenote-client.js ships as a follow-up patch.

Verification

  • npm test: 497 tests, 490 passing, 0 failing, 7 skipped (vs 448/441 in v1.2.4 — +49 new tests across the three features)
  • CI green on Node 20+22 across Ubuntu+Windows on each merged PR

Backwards compatibility

  • Every v1.2.4 surface (setup, --guided, --auth, --doctor, --batch, --resume, --verify, etc.) works identically
  • v2 progress.json files load unchanged
  • No new runtime dependencies
  • Bin path, module system, file layout: unchanged
Assets 2
Loading