When to use
Use this skill when preparing a release or sharing an installable build with artists.
Inputs
- •Source tree: repo root
- •Target version: synced with
bl_info["version"]andCHANGELOG.md
Steps
- •Clean previous artifacts: remove
dist/or any existing ZIPs for Lime Pipeline. - •Package only the add-on code: zip the
lime_pipeline/folder (exclude__pycache__,*.pyc, docs, and tests). - •Validate registration: ensure
lime_pipeline/__init__.pyimports and registers all classes and handlers referenced by the packaged modules. - •Smoke check (headless if possible): import
lime_pipelinein a Python session with Blender modules available; confirm no import-time errors. - •Name the artifact
lime-pipeline-<version>.zipand record the hash (e.g.,sha256sum).
Outputs
- •Installable ZIP placed under
dist/or a release drop folder - •Recorded hash for integrity verification