Publishing
Publish your package to the Lore registry.
Before Publishing
- Validate your package locally:
lore validate - Ensure you’re logged in:
lore login - Confirm your namespace ownership in the registry
Publish
lore publishThe CLI will:
- Run validation (same as
lore validate) - Create a
.lorearchive - Upload to the registry
- Return the package identifier on success
Versioning
Published versions are immutable — they cannot be overwritten. Always increment the version in manifest.yaml before publishing updates.
Use Semantic Versioning : MAJOR.MINOR.PATCH. Increment MAJOR for breaking changes, MINOR for new capabilities, PATCH for fixes.
CI/CD
For automated publishing from CI, set LORE_AUTH_TOKEN as a secret environment variable:
# Azure Pipelines
- script: |
lore publish
env:
LORE_AUTH_TOKEN: $(LORE_TOKEN)Namespaces
A namespace (e.g., m1cloud) is a publisher identity. Contact the registry admin to register your namespace. See Namespaces for details.