Menu
Compact lingtai-dev-guide release overview: when you are doing a release, the maintainer-authorization boundary, the version scheme, and a pointer to release-workflow for the full TUI/Portal + kernel publishing checklist, GitHub/PyPI/Homebrew steps, the required HTML release log, and the website release blog.
Nested lingtai-dev-guide reference for known implementation footguns: Bubble Tea v2 paste, textarea theming, dev-mode rebuilds, editable installs, migrations, localization, authorization gates, and config conventions.
Router for contributing to the LingTai project. Use this when you are about to change LingTai code or docs, set up a dev environment, navigate the Go TUI/portal repo or Python kernel, develop MCP addons, prepare a release, troubleshoot a running network, audit security, govern avatars, prepare a publication-bound release workflow, run a runtime self-check, get a PR review-ready, or steward a new skill. This is for developers and contributors; for end-user lessons, use tutorial-guide.
Nested lingtai-dev-guide reference for consequential LingTai releases: paired TUI/Portal + kernel release planning, clean worktrees, validation gates, GitHub/PyPI/Homebrew publishing boundaries, the required self-contained HTML release log, website release-log/blog drafting, and the reusable release blog template.
Nested lingtai-dev-guide reference for getting a PR review-ready: PR readiness gates, multi-model/daemon/Claude read-only review passes, self-contained local HTML explainers, PR body hygiene and gh pr edit troubleshooting, source-labeled deliverables with syntax/validation checks, and maintainer authorization boundaries for opening, editing, and merging PRs.
Nested lingtai-dev-guide reference for developer/operator runtime self-checks after a refresh, checkout, or preset/MCP change: probe which lingtai code is actually running, confirm the editable source and git HEAD, verify the active TUI/portal binary and dev-mode symlinks, rebuild the TUI from a clean release worktree, inspect MCP/addon module sources and tool surface, and report evidence safely with secrets redacted.
Nested lingtai-dev-guide reference for turning one-off experience into durable skills: when to write a skill vs leave it as notes, the router-vs-nested- reference pattern, distilling experience (归一) and session journals into triggered/executable SKILL.md files, de-privatizing and parameterizing local paths and human-specific details, a lightweight pre-publish benchmark/checklist, grooming shared-library candidates, and PR-ready skill cleanup.
| name | dev-guide-releasing |
| description | Compact lingtai-dev-guide release overview: when you are doing a release, the maintainer-authorization boundary, the version scheme, and a pointer to release-workflow for the full TUI/Portal + kernel publishing checklist, GitHub/PyPI/Homebrew steps, the required HTML release log, and the website release blog. |
| version | 2.0.0 |
Nested lingtai-dev-guide reference. Read this after the top-level router sends you
here. This page is the compact entry point; the full procedure lives in
../release-workflow/SKILL.md.
You are cutting or publishing a LingTai release across one or more of:
Lingtai-AI/lingtai (tags, GitHub release, Homebrew tap)Lingtai-AI/lingtai-kernel (PyPI package lingtai)Lingtai-AI/lingtai-telegram)lingtai-webPushing tags, creating GitHub releases, uploading to PyPI, committing to the Homebrew tap, and deploying website copy are external side effects. Proceed only after explicit maintainer authorization. If Jason says “直接 release / 先发 / publish it” (or equivalent), do the release and send short progress updates during long gates. Never print or share secrets/credentials. Do not let the website release log block an authorized software release unless Jason says the blog must land first.
vX.Y.Z); tags on the lingtai repo.
Homebrew builds from source — no binary assets needed.lingtai; version in
pyproject.toml. PyPI uploads are immutable — never reuse a published version.meta.json, tracked separately for
per-project (TUI+portal shared) and per-machine (global) migrations.../release-workflow/SKILL.md owns the complete, command-level procedure:
twine) upload, and Homebrew tap update;../release-html-log-template.html;../release-workflow/assets/release-blog-template.md.Start there for any real publish operation.