Miru supports continuous integration (CI) to automate various tasks, such as the creation of releases and their associated schemas.
CI pipelines leverage the Miru CLI to programmatically execute any CLI commands, which accept an API key for authentication.
Since the Miru CLI is the engine behind CI tasks, any tasks supported by the CLI can easily be automated in your CI pipeline.
Currently, GitHub Actions is the only officially supported CI tool. However, support for other CI tools is coming soon.
If you use a different CI tool, please reach out to [email protected] to request support for your tool.
API key authentication
When used in your CI pipeline, the CLI can be authenticated using an API key. Simply export the MIRU_API_KEY environment variable.
export MIRU_API_KEY=<your-api-key>
To create an API key for your CI pipeline, follow the instructions in the API keys section.
API key scopes
To determine the scopes to give an API key, find the CLI command you want to execute in the CLI Reference and consult its API key scopes section.
For example, if you want to execute the miru release create command in CI, visit the create release command’s API key scopes section. Last modified on February 5, 2026