界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
开发与工程 · SKILL.md

packaging-release

packaging-release

【开发与工程】Operate AnyLabeling install, test, packaging, PyInstaller, translation/resource, CPU/GPU wheel, macOS, and pre-publish release workflows.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: packaging-release description: "Operate AnyLabeling install, test, packaging, PyInstaller, translation/resource, CPU/GPU wheel, macOS, and pre-publish release workflows." disable-model-invocation: true metadata: disco-role: operating license: GPL 3.0

Packaging and release

Use this sub-skill when the task is about installing AnyLabeling for development, proving startup compatibility, building distributable artifacts, maintaining Qt resources/translations, or preparing CPU/GPU/macOS releases.

Route here for

  • Choosing the correct install variant: default CPU package, Linux/Windows GPU package, macOS CoreML extra, or developer tooling.
  • Running the local pre-publish gate: fresh install, unit tests, startup import smoke, optional real-model inference, and multi-Python checks.
  • Building wheels/sdists, checking package metadata, or understanding why the GPU package rewrites pyproject.toml to publish as anylabeling-gpu.
  • Building PyInstaller executables, macOS folder-mode output, and diagnosing bundled onnxruntime native DLL failures.
  • Regenerating Qt translations/resources and checking for the PySide6 toolchain used to rebuild a PyQt6 resource module.

Route elsewhere

  • Manual annotation, label JSON, canvas behavior, and dataset export belong to annotation-ui-and-data.
  • Auto-labeling model configs, downloads, SAM/YOLO inference, and model registry behavior belong to auto-labeling-models.
  • PyPI upload credentials, release approval, or tag creation are outside this skill; this skill explains the checks and build mechanics but does not authorize publishing.

Read first

Bundled helper

  • scripts/check_language_tools.py checks whether the translation/resource toolchain is available without mutating generated files. Run it before following the resource regeneration recipe.

Keep release commands scoped to a disposable or intentionally prepared checkout. Some maintainer scripts mutate package metadata or generated resources; read the linked references before running them.

我的收藏