AI Disclosure: This page was generated by an LLM and may contain inaccuracies. Hand-crafted documentation will be implemented over time on the road to 1.0

Build a complete release artifact set

Build release artifacts from a clean, versioned checkout. Publish only the files Phials supports.

Run the release build

From the plugin project root:

npm ci
npm run check
npm run test:run
npm run build
npm run validate

build creates a clean dist/; validate checks the exact output. Do not copy an older artifact forward or hand-edit generated output.

Include the required files

Every release contains:

dist/
├── manifest.json
└── main.js

Add optional artifacts only when the plugin supplies them:

dist/
├── manifest.json
├── main.js
├── styles.css
├── theme-slate-light.json
├── theme-slate-light.css
├── theme-slate-dark.json
└── theme-slate-dark.css

Artifact	Contract
`manifest.json`	Strict manifest for this exact plugin version
`main.js`	Loadable ES module with the plugin’s default export
`styles.css`	Optional compiled global CSS for plugin interfaces
`theme-<slug>.json`	Optional flat theme metadata asset
`theme-<slug>.css`	Required matching CSS half of a theme pair

Theme pairs use one identical lowercase kebab-case slug. Follow Package and test theme release artifacts when the plugin contributes themes.

Exclude development files

Do not attach:

source files or source maps
node_modules/
package-manager lockfiles
test files or fixtures
local environment or editor files
SDK source declarations
screenshots or release-note drafts
a zip or tar archive containing the real artifacts

Release notes belong in the GitHub release body. Images used by those notes may be uploaded as release-description media, but they are not plugin release artifacts.

Verify the artifact set as one unit

The validator confirms:

required and optional filenames
no unsupported files
manifest, package, module identity, and version alignment
compatibility and permission fields
loadable single-entry ES-module shape
Svelte runtime exports when components are present
CSS parsing and global-scope rules
complete theme pairs and required theme tokens

Use Build and validate release artifacts for the detailed checks.

Freeze the candidate

Record an immutable inventory:

npm run release:inventory

The command records each artifact filename, byte size, and SHA-256 checksum without modifying dist/. Review the inventory and keep it with the release verification record.

Attach files directly from the verified dist/. If a later command rewrites, minifies, renames, signs, or otherwise changes an artifact, it is a new candidate and needs a new validation and inventory.

Phials prefers attached manifest.json and main.js from the latest GitHub release. Attach the complete optional set as well; do not rely on repository files or a raw-tag fallback to supply missing assets.