mazurov/Command Launcher Package Action

Automate Command Launcher package lifecycle - validate manifests, create .pkg releases, and publish to OCI registries

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
packages-directoryDirectory containing packages. Empty (default) = auto-detect: single package (root has manifest.mf) or multi-package (scan subdirectories). Set to specific path for multi-package repos with custom structure.no""
validate-onlyOnly validate manifests without packagingnofalse
package-formatPackage format: zip (creates ZIP archives), oci (pushes to OCI registry), or bothnozip
oci-registryOCI registry hostname (e.g., ghcr.io)noghcr.io
packages-namespacePackages namespace path in OCI registry. Defaults to repository name (owner/repo) when emptyno""
oci-usernameOCI registry username. Defaults to GitHub actor when emptyno""
oci-tokenOCI registry token/password. Defaults to GITHUB_TOKEN env var if setno""
force-releaseForce recreate releases by deleting existing releases and tags first (default: false)nofalse
namedescription
validated-packagesJSON array of validated package directories
valid-countNumber of valid packages
invalid-countNumber of invalid packages
packaged-artifactsJSON array of created artifact paths with metadata
package-countNumber of packages created