Repository navigation
Releases
Releases · runnerback/content-studio
3.12.3 - License service moved to api.runfast.ren
- License service domain. The metered Xiaohongshu / X publishing uses the author's license service, which moved from
api.runfast.xyz/licensetoapi.runfast.ren/license(the server was relocated on 2026-11-04 and the old domain stops working when the old server is shut down). Without this update the plan list on the "Xiaohongshu / X (browser extension)" settings page fails to load and redeeming an Afdian order number returns a network error. - Update the Crosspost extension to 3.1.7 too. Quota metering is requested by the browser extension; older versions still point at the old domain and refuse to publish with "cannot reach the license service".
- License keys and the daily count live on the server and are unchanged. No settings migration. WeChat articles, image cards, Feishu sync and AI layout never contact this service and are not affected.
- README network-use disclosure and the quota guide now name the new domain.
3.12.2 - Fix the community directory source review (dependency install)
- Directory review fix. 3.12.1 failed the community directory's automated source review with "Source review dependency installation failed": the repository could only be installed with
npm install --legacy-peer-depsbecause the unusedeslint-plugin-obsidian(an unrelated react-obsidian lint plugin that pins ESLint 8) conflicted with ESLint 9. The package is removed,@types/nodefollows Vite's supported range, andnpm install/npm cinow resolve without flags. CI and the release workflow were updated accordingly. - No functional changes to the plugin.
3.12.1 - Result push-back from the Crosspost extension, extension self-check in settings
- Result push-back. With Crosspost 3.1.0+ (bridge protocol v1.1) the extension reports each platform's outcome over the bridge as it finishes. A note delivered to the extension is still recorded as
publish_status: pendingfirst; when the result arrives its frontmatter moves to confirmed (platform_<name>: 1) or topublish_failed, and the publishing dashboard shows the failure. Results that arrive after Obsidian was restarted are only shown as a notice and do not touch the document. Older extensions keep the 3.12.0 behaviour (pending until you check the draft box yourself). - Extension self-check in settings. "Test connection" now shows, per platform, the extension's probe result (signed in, creator tab open, X draft endpoint in sync with x.com) and the last publish outcome, from the bridge's
health.adapters. Older extensions simply show nothing extra. - Protocol version check. The extension reports
capabilities.protocolVersionon handshake; a different major version is rejected and "Test connection" asks you to update the extension or the plugin. - Internal:
services/bridge-sync-tasks.jsmapssyncId→ note;normalizeAdapterHealthSnapshotinservices/wechatsync-settings.js; new dictionary keys undermultiPlatform.health*.
3.12.0 - Desktop-only, 1.3 MB bundle, English UI for settings, publishing dashboard
- Bundle size 3.8 MB → 1.3 MB. Math now renders with Obsidian's built-in MathJax (CHTML) instead of a bundled SVG engine; formulas are rasterized to PNG only when copying to WeChat or saving a draft through the API. The built-in Xiaohongshu card backgrounds were re-encoded to WebP.
- Desktop only (
isDesktopOnly: true). The local WebSocket bridge and Feishu image handling need desktop APIs; the mobile app previously crashed on those paths. - Honest status for the companion extension. Until the Crosspost browser extension is released, the settings page and the publish modal say so instead of listing build-and-sideload steps. Cards delivered to the extension are recorded as
publish_status: pending/publish_pendingand the notice says "awaiting confirmation", because the extension only acknowledges receipt. - Settings consolidated. Phone frame and image watermark moved into the preview panel's advanced options and apply immediately; dead settings (Feishu smart update / double-link / debug logging, legacy single-account fields) removed; the extension page is named "Xiaohongshu / X (browser extension)".
- Settings, commands and the Xiaohongshu card settings follow Obsidian's language: Chinese (Simplified or Traditional) → Simplified Chinese, anything else → English. Dictionaries live in
services/locales/. - Publishing dashboard (
Open publishing dashboardcommand, toolbar button): targets from frontmatterplatform(arrays allowed for multi-platform posts), published / awaiting / not-yet columns, filters by platform, status and keyword. - AI layout cost visibility: token usage per run and a per-device total in settings, optional price per million tokens for a cost estimate; cached layouts generated by an older skill version are flagged as outdated.
- Code structure: the entry file and the AI layout service were split into focused modules; docs (CLAUDE.md, CONTRIBUTING, RELEASING, guides) refreshed and a user-facing CHANGELOG added.
3.11.17 - Auto-switch toggle moved to the top level of 样式设置
- The "按文档属性自动切换预览平台" toggle introduced in 3.11.16 applies to every platform, so it now sits directly under 样式设置 next to the 公众号排版 / 小红书图卡 entries instead of inside the 公众号排版 page. Behaviour is unchanged.
3.11.16 - Preview platform follows the note's platform property
- Switching notes now switches the preview platform automatically: the panel reads the note's frontmatter
platform(wechat/rednote/x, also the toolbar labels 公众号 / 小红书 / X and common aliases such asxiaohongshu/twitter) and selects the matching mode. Notes without the property, or with an unrecognised value, keep the current mode, and the toolbar dropdown still works as before. Editing the property while the note is open applies immediately. - New toggle in 样式设置 → 公众号排版 → 预览模式: "按文档属性自动切换预览平台" (on by default). Its description documents the convention so other users can adopt it in their own notes.
- Tests:
tests/platform_property.test.js,tests/preview_mode_auto_switch.test.js.
3.11.15 - Zero warnings on the directory scanner's own environment
- The community directory scans the repository without
@types/nodeand without the gitignored build outputs. The remaining 227 warnings it still reported on 3.11.14 all came from that difference:Buffer/require(Node globals) and ES2019+ methods (trimStart,flatMap,Object.fromEntries,Array.prototype.at) resolved locally only because@types/nodehappened to bring them along. tsconfig.jsonnow declareslib: ES2022 + DOMexplicitly;types/node-globals.d.tsadds mergeable declarations for the Node globals the desktop-only code paths use;tsconfig.scan.json(types: []) makes the local scan and the release guard see exactly what the directory sees. Result on that environment: 0 problems.- Transitive dependency
@xmldom/xmldom(via mathjax → speech-rule-engine) pinned to 0.9.12 to clear the advisory shown on the directory. - No functional changes.
3.11.14 - Directory scan cleared to zero (typed, no suppressions)
- The local reproduction of the Obsidian community directory scan (
npm run scan:directory, obsidianmd recommended + typescript-eslint type-checked rules, now run with--no-inline-config) reports 0 problems, down from 1936 once the findings hidden behindeslint-disablecomments are counted. Everyeslint-disablecomment and everyanywas removed from the plugin source; nothing is suppressed. - Types at the source: the view mixins' method surface is merged into the
AppleStyleViewclass (types/view-augment.d.ts), plugin members are declared in theAppleStylePluginconstructor, and the AI-layout / WeChat / Feishu / wechatsync payload helpers return real JSDoc types instead ofany. The mixin type generator no longer picks up a previous method's@returns. - Async hygiene: event handlers no longer pass async callbacks (
() => { void … }), floating promises are awaited or explicitly ignored, andasyncfunctions withoutawaitbecame plain functions returning a Promise. - 小红书图卡 settings UI is a plain render class (
RedSettingsPanel) hosted by the main settings page instead of a deprecatedPluginSettingTab.display()subclass. - UI copy rewritten in Chinese where the scanner's sentence-case rule would otherwise lowercase product terms (e.g. "开发者 ID 与密钥", "提示词", "AI 服务商", "应用 ID / 应用密钥").
npm run review:guard(run by the release workflow) now includes the directory scan, so a release cannot be tagged with new findings. The gitignoredservices/ai-layout-runtime/generated-skills.jsgets a committed.d.ts, so the scan resolves the same types in CI and on the directory (where the generated file does not exist) as it does locally. Supersedes the 3.11.13 tag, whose release workflow stopped at this check.- No functional changes.
3.11.12 - Code quality pass against the directory scanner
- Reproduced the Obsidian community directory scan locally (
npm run scan:directory, obsidianmd recommended + type-aware rules) and worked through it: total findings 4987 → 1498,no-unsafe-call1179 → 185. - Rednote (小红书) module: Obsidian DOM helpers instead of
document.createElement,window.*timers,setIconinstead ofinnerHTMLSVGs, no Nodeeventsdependency, typed theme style sections (wasany). - Plugin views:
thisinside the view mixins is now typed (types/view-mixins.d.ts, generated bynpm run generate:view-typesand verified inpretest); view members declared in the constructor; the Obsidian module is typed instead ofany. - Removed lifecycle
console.logs; bridge diagnostics moved toconsole.debug. - No functional changes.
3.11.11 - Release workflow publishes only after assets are attached
- No plugin code changes since 3.11.10.
- The release workflow now creates the GitHub Release as a draft, verifies
main.js/manifest.json/styles.cssare attached, and only then publishes it. The Obsidian community directory reads release assets the moment a release is published; 3.11.10 was reviewed during the upload window and wrongly reported as missingmain.jsandmanifest.json.