Lando Headless CLI
The Lando Headless CLI is a command-line tool for interacting with Lando via the automation API.
🐛 Bug Reports
Please file bugs in Bugzilla under Conduit :: Lando
Report issues or request enhancements in #engineering-workflow on Slack or #conduit on Matrix.
🔧 Installation
Install the CLI tool from PyPI using uv, pip, or pipx.
uv tool install lando_cli
Confirm the tool is installed locally.
lando --version
🛠️ Development
This project uses uv for package and virtual environment management.
Install all dependencies, including dev and test groups:
uv sync --group code-quality --group testing
Run the test suite:
uv run pytest
Run the linter and formatter:
uv run ruff check .
uv run black --check .
🔐 Configuration
The CLI expects a config file at ~/.mozbuild/lando.toml with the following options:
[auth]
api_token = "TOKEN"
user_email = "ldap_user@mozilla.com"
Alternatively, you can supply the values as environment variables:
LANDO_HEADLESS_API_TOKENLANDO_USER_EMAILLANDO_URL(optional, defaults tohttps://lando.moz.tools)
🚀 Usage
Run lando --help for an overview of available commands.
Run lando <COMMAND> --help for help with each command, including examples.
push-commits
Push new commits to a Lando repo.
Create new commits against the specified branch locally. The currently checked out branch will be used for the push, and the upstream branch will be used as the base.
lando push-commits --lando-repo firefox-autoland
With a release branch:
lando push-commits --lando-repo firefox-beta --relbranch FIREFOX_64b_RELBRANCH
push-tag
Push new tags to the specified repository.
lando push-tag --lando-repo firefox-main --tag-name TAG_NAME --tag-sha sha12345
push-merge
Push merge actions to the specified repository.
Running without any options will detect the merge target and commit message
using the current HEAD.
lando push-merge --lando-repo firefox-main
Use --target-commit and --commit-message to create the merge in Lando
without detecting the change in your local repo.
lando push-merge --lando-repo firefox-main --target-commit SHA --commit-message "Merge"
check-job
Check the status of a previously submitted job.
lando check-job 123
Release files for lando-cli 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lando_cli-0.4.1.tar.gz | 47.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lando_cli-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.2 kB
Release files / lando_cli-0.4.1.tar.gz
| Download URL | lando_cli-0.4.1.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec7cf57726ef1bb495605598f9c43d2a4ab1af8b346511e32ebdab09700aa94b
|
|
BLAKE2b-256 checksum How to use checksums |
a5742f0b0027ed2e69e81bd616ee46c06089af48f51c20ff0e6dcfda9b997317
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / lando_cli-0.4.1-py3-none-any.whl
| Download URL | lando_cli-0.4.1-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
760dda77da7e2cf57a453ac6bc982e97ee8bbfa087f0e62edfa5aa67adbfcf86
|
|
BLAKE2b-256 checksum How to use checksums |
94b71093db09d8b0f66880bad198b454e089e8d874c5545912d42f6c7c3116a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency log