Phials plugin documentation
User guide
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

Package and publish

Phials installs a plugin from the matching release artifacts attached to a versioned GitHub release. The community registry identifies the repository; it is not the plugin package itself.

  • Configure the plugin manifest defines identity, public metadata, compatibility, permissions, and validation.
  • Prepare a release aligns versions, builds the complete artifact set, documents changes, and applies the release gate.
  • Publish your plugin publishes a GitHub release, submits the registry entry, and verifies the same installation path users receive.
  • Maintain a published plugin covers upgrades, permission and compatibility changes, data migrations, broken releases, ownership, and unlisting.

Keep manifest.json, main.js, optional styles.css, and any supported theme assets from one build together. A release is complete only when its identity and version agree across every artifact.