Registry
The central registry stores package manifests that point to Git repositories.
Registry Location
Section titled “Registry Location”https://github.com/yanlvl99/lune-custom-build/tree/main/manifestEach package has a JSON file: manifest/<package-name>.json
Manifest Format
Section titled “Manifest Format”{ "name": "colors", "description": "ANSI color utilities for Luau", "repository": "https://github.com/someone/lune-colors.git"}Fields
Section titled “Fields”| Field | Required | Description |
|---|---|---|
name | Yes | Package name (must match filename) |
description | No | Brief description |
repository | Yes | Git repository URL |
Note: Version is not specified in the manifest. The installer fetches the latest semver tag from the repository.
Adding a Package to Registry
Section titled “Adding a Package to Registry”- Fork the registry repository
- Add your manifest file to
/manifest/<name>.json - Open a Pull Request
Example PR
Section titled “Example PR”Add 'my-package' to registry
manifest/my-package.json:{ "name": "my-package", "description": "My awesome Lune package", "repository": "https://github.com/me/my-package.git"}How Resolution Works
Section titled “How Resolution Works”- User runs
lune --install colors - Installer fetches
manifest/colors.jsonfrom registry - Reads
repositoryfield - Lists remote git tags
- Parses tags as semver, sorts descending
- Clones at the highest version tag
Self-Hosted Registry
Section titled “Self-Hosted Registry”You can use a custom registry by modifying the REGISTRY_REPO constant in the Lune source code.