Skip to content
cccskills
FreePublished on GitHub

release

Cross-platform release, version bumping, changelog maintenance, and production deployment protocol for md-editor

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40 stars(GitHub 40 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md7.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Multi-Platform Release & Deployment Skill

This skill guides agents through the end-to-end lifecycle for versioning, changelog generation, tagging, CI/CD pipeline monitoring, and production deployment across all client platforms in the md-editor workspace.

1. Operating Principles

  1. Strict Platform Symmetry: Every client platform (desktop, android, web, site, utools, worker) has a clear, isolated release lifecycle and namespace.
  2. Single Source of Truth in Git:
    • NEVER build or upload binaries out-of-band without committing the version bump and changelog to the Git repository.
    • Version files (package.json, build.gradle.kts, tauri.conf.json, Cargo.toml) and CHANGELOG.md (plus CHANGELOG_EN.md) must be updated and committed together.
  3. Changelog-Driven Presentation:
    • The official website (site) and distribution portal read directly from each platform's CHANGELOG.md at build/ISR time.
    • A release is only complete when its user-facing changelog entry is present in both Chinese (CHANGELOG.md) and English (CHANGELOG_EN.md).
  4. Pre-Release Quality Gate:
    • Working tree must be clean.
    • Must be on the latest main branch.
    • pnpm verify (lint + test + typecheck) must pass 100% before any release command is executed.

2. Multi-Platform Release Matrix

Platform / TargetFull Release CommandVersion Bump OnlyGit Tag PatternCI/CD WorkflowVersion Files & ChangelogDistribution Target
Desktop Apppnpm release:desktoppnpm release:desktop:versionv* (e.g. v0.12.1).github/workflows/release-desktop.ymlapps/desktop/package.json<br>src-tauri/tauri.conf.json<br>src-tauri/Cargo.toml<br>apps/desktop/CHANGELOG*.mdCloudflare R2 (/inkpoint/desktop/)<br>Homebrew Tap<br>GitHub Releases
Android Apppnpm release:androidpnpm release:android:versionandroid-v* (e.g. android-v0.2.0).github/workflows/release-mobile.ymlapps/mobile/android/app/build.gradle.kts<br>apps/mobile/android/CHANGELOG*.mdCloudflare R2 (/inkpoint/android/)<br>Distribution Gateway
Web Playgroundpnpm release:webpnpm release:web:version<br>pnpm release:web:publishweb-v* (archival tag only).github/workflows/release-web.ymlapps/web/package.json<br>apps/web/CHANGELOG*.mdVercel Production (editor.justdev.cn/playground)
Official Sitepnpm release:siteN/ATriggered on release or manualVercel CLI Prebuilt DeploySourced from Desktop, Android & Web changelogsVercel Production (editor.justdev.cn & editor.jiaqi.im)
Distribution Workerpnpm deploy:workerN/AManual / Infrastructure deployCloudflare Worker CLIinfra/distribution-workerCloudflare Edge (download.justdev.cn & download.jiaqi.im)
uTools PluginManual Reviewapps/utools/package.jsonutools-v*.github/workflows/release-utools.ymlapps/utools/package.json<br>apps/utools/CHANGELOG*.mduTools Developer Center (manual submission)

3. Platform Release Workflows

3.1 Desktop Release (apps/desktop)

  1. Pre-check: Ensure working tree is clean and pnpm verify passes.
  2. Execute release:
    # Interactive mode (prompts for patch / minor / major / beta / notes)
    pnpm release:desktop
    
    # Or non-interactive CLI:
    pnpm release:desktop patch --notes "修复已知缺陷"
    
  3. What happens automatically:
    • Updates version in apps/desktop/package.json, tauri.conf.json, Cargo.toml.
    • Prepends new version block into apps/desktop/CHANGELOG.md and apps/desktop/CHANGELOG_EN.md.
    • Creates commit chore(release): release vX.Y.Z and annotated tag vX.Y.Z.
    • Pushes tag to origin, triggering .github/workflows/release-desktop.yml.
    • GitHub Actions builds macOS (DMG + updater), Linux (AppImage + DEB), and Windows (Setup EXE).
    • Uploads artifacts to Cloudflare R2, updates version.json, purges CDN cache, and triggers pnpm release:site.

3.2 Android Release (apps/mobile/android)

  1. Pre-check: Ensure working tree is clean and pnpm verify passes.
  2. Execute release:
    # Interactive mode:
    pnpm release:android
    
    # Or non-interactive CLI:
    pnpm release:android patch --notes "优化移动端编辑器体验"
    
  3. What happens automatically:
    • Increments versionCode and updates versionName in apps/mobile/android/app/build.gradle.kts.
    • Prepends new version block into apps/mobile/android/CHANGELOG.md and apps/mobile/android/CHANGELOG_EN.md.
    • Creates commit chore(android): release android-vX.Y.Z and annotated tag android-vX.Y.Z.
    • Pushes tag to origin, triggering .github/workflows/release-mobile.yml.
    • GitHub Actions builds release APK, signs it, and uploads Inkpoint_X.Y.Z.apk to Cloudflare R2.
    • Updates version.json and releases.json, purges CDN cache, and triggers pnpm release:site.

3.3 Web Playground Release (apps/web)

  1. Scheme A - Vercel CLI Direct Deploy (Recommended):
    pnpm release:web
    
    Directly pulls production environment, prebuilds, and deploys to Vercel production without polluting GitHub Releases.
  2. With Version & Changelog Archive:
    pnpm release:web:publish patch --notes "新增 MDX 动态预览支持"
    
    Updates apps/web/package.json, updates apps/web/CHANGELOG*.md, pushes web-v* archival tag, and deploys.

3.4 Official Site Deployment (site)

  1. Deploy Site:
    pnpm release:site
    
  2. Mechanics:
    • Uses Vercel CLI with prebuilt output (pull -> build --prod -> deploy --prebuilt).
    • Reads apps/desktop/CHANGELOG.md, apps/mobile/android/CHANGELOG.md, and apps/web/CHANGELOG.md.
    • /changelog route uses Next.js ISR (export const revalidate = 300) for high-performance edge caching.

3.5 Distribution Worker Deployment (infra/distribution-worker)

  1. Deploy Worker:
    pnpm deploy:worker
    
  2. Deploys updated Cloudflare Worker handling download redirects, device directories, and release API metadata.

4. Post-Release Verification Checklist

After the release workflow runs, verify each checkpoint:

  1. GitHub Actions Workflow:
    gh run list --limit 3
    gh run watch <run_id>
    
    Ensure all matrix jobs (build, package, upload, site deploy) are green.
  2. Distribution Edge API:
    curl -s https://download.jiaqi.im/api/inkpoint/releases | jq '{latestDesktopVersion, latestAndroidVersion}'
    
    Confirm latestDesktopVersion and latestAndroidVersion match the expected versions.
  3. Direct Download Links:
    • Desktop: https://download.jiaqi.im/inkpoint/desktop/macos/latest
    • Android: https://download.jiaqi.im/inkpoint/android/latest
  4. Website Rendering:
    • Home page: check that the download CTA displays the correct version badge.
    • Changelog page (/changelog): verify all platform tabs (Desktop, Android, Web) show the newly released version and notes.

5. Troubleshooting & Rollback SOP

  • Broken Release CI Job:
    1. Inspect failed logs: gh run view --log-failed <run_id>.
    2. If caused by network timeout or temporary R2 token glitch, re-run failed jobs via GitHub CLI or Actions UI.
    3. If code or script error, fix on a fix/<description> branch, land PR to main, and re-trigger release.
  • R2 Edge Cache Stale: Run cache purge manually:
    node scripts/release/purge-download-cache.mjs
    
  • Never delete or rewrite published tags on remote: Always increment with a new patch release (e.g. 0.12.2 or 0.2.1) to preserve immutable download history.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

[OMX] Run an anti-slop cleanup/refactor/deslop workflow

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40Updated Oct 28, 2026

[OMX] Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40Updated Oct 28, 2026

ask

Free

[OMX] Ask a local external advisor CLI (Claude or Gemini) and capture a reusable artifact

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40Updated Oct 28, 2026

[OMX] Strict autonomous loop: $deep-interview -> $ralplan -> $ultragoal (+ $team if needed) -> $code-review -> $ultraqa

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40Updated Oct 28, 2026

[OMX] Stateful validator-gated research loop with native-hook persistence

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40Updated Oct 28, 2026

[OMX] Durable professor-critic research workflow over Codex goal mode without reviving deprecated omx autoresearch

The English summary is being prepared. Showing the original description.

wmasfoe/md-editor40Updated Oct 28, 2026

See all skills by wmasfoe

Report a problem with this skill