Publishing
Overview
From a publisher profile and signing key to a signed, moderated, installable marketplace package.
The CLI takes an extension from source to the marketplace: create a publisher, register a
signing key, pack a signed .vpkg, and publish it for moderation.
The publishing flow
Create a publisher
verentis publisher create registers your publisher identity — the namespace your packages live
under (e.g. acme/my-app).
Register a signing key
verentis keygen generates an Ed25519 key and registers its public half. Publishers with a
registered key must sign their uploads.
Scaffold & pack
verentis init scaffolds a project; verentis pack produces a signed .vpkg (optionally sealed
with --encrypt).
Publish
verentis publish my-app-0.1.0.vpkg uploads it. New versions are Submitted for moderation; once
approved the marketplace countersigns them and they become installable.
What you'll manage
Create a publisher and manage Ed25519 signing keys.
Scaffold, pack, sign, encrypt, and publish.
Versions, visibility, deprecation, stats, search and install.
What's inside a package and how it's signed.
Building the extension itself
These commands ship apps and engines. The manifests and SDKs you build against are documented in the developer documentation.