@bobfrankston/rmfmail 1.2.278 → 1.2.279

package/.commitmsg

@@ -1,29 +1,16 @@
-TinyMCE 8.6.0 → 8.8.2
+build-tinymce: report which TinyMCE and language-pack versions were copied
 
-Routine maintenance releases — no security advisories, no breaking changes
-(all within major 8). Four of the fixes land on paths mailx actually uses:
+Both specs are caret ranges, so the resolved version moves on its own whenever
+npm re-resolves the tree — tinymce sat at 8.6.0 for weeks under a ^8.5.0 spec
+with nothing to notice ("do you track updates for TinyMCE?", Bob 2026-08-23).
 
-- The menubar could wrap onto multiple rows on narrow viewports or at high
-  browser zoom, leaving little or no visible editable area (8.8.1). Same class
-  of failure as the v1.2.264 "body must fill the iframe" bug, and compose is
-  routinely used zoomed.
-- CSS custom property names and colour values in a style attribute were
-  lowercased when parsed (8.7.0) — that is quoted mail passing through a
-  reply/forward.
-- Copying or dragging in an image didn't set width/height on the tag (8.7.0),
-  which the inline-image → cid path then had to carry.
-- The link plugin threw a querySelectorAll syntax error on anchors containing
-  semicolons (8.8.0). Mail bodies are full of odd links.
+Pinning exact would only trade silent drift for silent staleness: no more patch
+fixes, and the surprise moves to whoever edits the pin. A dependency bot is the
+wrong shape too — those work by filing PRs, and this repo publishes from the
+local tree with direct commits.
 
-Also: undo not restoring the selection, deleting a newline in a list item
-eating the item, and the emoticons dialog's 300-item cap (we load that plugin).
-
-Verified before publishing: all 17 plugins we request still exist in 8.8.2, the
-dom model is unchanged, and the package still ships no langs/ directory — the
-61 packs added in 1.2.277 come from tinymce-i18n and are copied after the tree,
-so the re-copy keeps them (62 files present, manifest included).
-
-The spec moves from ^8.5.0 to ^8.8.2. The old floor already permitted 8.8.2;
-the tree had simply drifted at 8.6.0 with nothing to notice it, which is what
-prompted this. Raising the floor makes the intent explicit rather than leaving
-a fresh install free to resolve lower.
+So make it visible where it already costs nothing. Every publish archives its
+build transcript to c:\temp\rebuild\, and build-tinymce.js already prints what
+it copied; it now prints the resolved versions of tinymce and tinymce-i18n as
+well. "Which TinyMCE shipped in 1.2.277?" is answerable from the log, with no
+network call at build time and nothing to maintain.

package/bin/build-tinymce.js

@@ -18,6 +18,21 @@ const dst = path.join(root, "client", "lib", "tinymce");
 const langSrc = path.join(root, "node_modules", "tinymce-i18n", "langs8");
 const langDst = path.join(dst, "langs");
 
+// Which versions went into this build. The spec is a caret range, so the
+// resolved version moves on its own whenever npm re-resolves the tree — it sat
+// at 8.6.0 for weeks under a ^8.5.0 spec with nothing to notice (Bob
+// 2026-08-23: "do you track updates for TinyMCE?"). Pinning would only trade
+// silent drift for silent staleness. Printing it puts the answer in the build
+// transcript every publish archives, at no cost and with no network call.
+// (Claude Code 2026-08-24)
+function pkgVersion(name) {
+    try {
+        return JSON.parse(fs.readFileSync(path.join(root, "node_modules", name, "package.json"), "utf-8")).version;
+    } catch {
+        return "unknown";
+    }
+}
+
 if (!fs.existsSync(src)) {
     console.error(`build-tinymce: source not found at ${src} — run npm install first`);
     process.exit(1);
@@ -53,7 +68,7 @@ if (fs.existsSync(langSrc)) {
     }
     langs.sort();
     fs.writeFileSync(path.join(langDst, "index.json"), JSON.stringify(langs, null, 2) + "\n");
-    console.log(`build-tinymce: copied ${langs.length} language packs → client/lib/tinymce/langs/`);
+    console.log(`build-tinymce: copied ${langs.length} language packs (tinymce-i18n ${pkgVersion("tinymce-i18n")}) → client/lib/tinymce/langs/`);
 } else {
     // Never silently ship an editor whose language menu is empty.
     console.error(`build-tinymce: WARNING no language packs at ${langSrc} — run npm install; the editor will be English-only`);
@@ -66,4 +81,4 @@ function tally(p) {
     else { count++; bytes += st.size; }
 }
 tally(dst);
-console.log(`build-tinymce: copied ${count} files (${(bytes / 1024 / 1024).toFixed(1)} MB) → client/lib/tinymce/`);
+console.log(`build-tinymce: copied tinymce ${pkgVersion("tinymce")} — ${count} files (${(bytes / 1024 / 1024).toFixed(1)} MB) → client/lib/tinymce/`);

package/npmchanges.md

@@ -564,3 +564,35 @@ Harper (English only) are untouched, and Quill/tiptap have no localized chrome.
 tests/tinymce-langs.test.ts pins the resolution against the real manifest.
 Needs rmf-tiny 0.1.52 for the adapter's `language` option.
 
+## v1.2.278 — 2026-08-25
+
+TinyMCE 8.6.0 → 8.8.2
+
+Routine maintenance releases — no security advisories, no breaking changes
+(all within major 8). Four of the fixes land on paths mailx actually uses:
+
+- The menubar could wrap onto multiple rows on narrow viewports or at high
+  browser zoom, leaving little or no visible editable area (8.8.1). Same class
+  of failure as the v1.2.264 "body must fill the iframe" bug, and compose is
+  routinely used zoomed.
+- CSS custom property names and colour values in a style attribute were
+  lowercased when parsed (8.7.0) — that is quoted mail passing through a
+  reply/forward.
+- Copying or dragging in an image didn't set width/height on the tag (8.7.0),
+  which the inline-image → cid path then had to carry.
+- The link plugin threw a querySelectorAll syntax error on anchors containing
+  semicolons (8.8.0). Mail bodies are full of odd links.
+
+Also: undo not restoring the selection, deleting a newline in a list item
+eating the item, and the emoticons dialog's 300-item cap (we load that plugin).
+
+Verified before publishing: all 17 plugins we request still exist in 8.8.2, the
+dom model is unchanged, and the package still ships no langs/ directory — the
+61 packs added in 1.2.277 come from tinymce-i18n and are copied after the tree,
+so the re-copy keeps them (62 files present, manifest included).
+
+The spec moves from ^8.5.0 to ^8.8.2. The old floor already permitted 8.8.2;
+the tree had simply drifted at 8.6.0 with nothing to notice it, which is what
+prompted this. Raising the floor makes the intent explicit rather than leaving
+a fresh install free to resolve lower.
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/rmfmail",
-  "version": "1.2.278",
+  "version": "1.2.279",
   "description": "Local-first email client with IMAP sync and standalone native app",
   "type": "module",
   "main": "bin/mailx.js",