> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/release-notes/cli/2025.md).
# 2025
## v1.0.4 (2025-11-07)
### Features
* The new `lunar clear-cache` command resets the CLI's local caches.
* Collectors and policies that specify an `image` in their configuration now run inside Docker containers, including when run locally with `lunar collector dev` and `lunar policy dev`; Docker must be available for containerized dev runs. See [Containerized script execution](/release-notes/product/2025.md#product-containerized-script-execution).
* The new `lunar sql connection-string` command prints the PostgreSQL connection string for the SQL API.
* The new `lunar sql refresh` command rebuilds the materialized tables behind the SQL API.
### Improvements
* Cached repository clones now check for upstream updates instead of serving stale content.
* `lunar collector dev` now merges the component JSON deltas if there are multiple collections, mirroring how the Hub merges them; disable with `--merge=false`.
### Bug fixes
* Fixed an issue with searching parent directories for `lunar-config.yml`.
* GitHub tokens are now refreshed automatically for cached repository clones; previously, cached git directories could be left with expired tokens.
## v1.0.3 (2025-09-23)
### Features
* A new `--verbose` flag on `lunar collector dev` and `lunar policy dev` prints the script's own output alongside the command's results.
* Hub connection settings can now be defined under a `hub` section in `lunar-config.yml`; the CLI resolves connection settings with flags taking precedence over environment variables, which take precedence over the config file.
### Improvements
* Script dependencies are installed ahead of execution for all runtimes, with improved locking, making collector and policy runs faster and more reliable.
* `lunar collector dev` and `lunar policy dev` reuse previously cloned repositories and installed configurations between runs, making repeated runs much faster; a new `--no-cache` flag forces a fresh clone and install.
* `lunar policy dev` formats check results as a list instead of a table.
* `lunar hub run-code-collectors` accepts `--pr-max-age-days` and `--include-pr-commits`, matching `lunar hub pull`; the flag replaces the previous `--max-age-days`/`-m`.
* Collector and policy scripts run with a defined working directory and receive the `LUNAR_PLUGIN_ROOT` environment variable pointing at their plugin's root.
### Bug fixes
* File permissions and symlinks are preserved when plugin files are copied during installation.
## v1.0.2 (2025-09-04)
### Bug fixes
* Releases include the macOS (Apple silicon) binary again; it was missing from the v1.0.1 release.
## v1.0.1 (2025-09-03)
### Improvements
* Collector and policy scripts now have a Lunar-managed bin directory on their `PATH`, configurable via the `LUNAR_BIN_DIR` environment variable — install a custom binary there and scripts can invoke it directly.
## v1.0.0 (2025-09-03)
### Features
#### Initial public release
The `lunar` CLI and the CI/CD Tracer binary are now publicly distributed through GitHub releases on `earthly/lunar-dist`. This first release ships `lunar` for Linux (amd64) and macOS (Apple silicon), plus the CI/CD Tracer (`lunar-ci-agent`) for Linux (amd64).
The CLI provides commands for developing and testing collectors and policies locally (`lunar collector dev`, `lunar policy dev`), inspecting Component JSON (`lunar component get-json`), submitting data out of band (`lunar collect`), and administering the Hub configuration (`lunar hub pull`). The CI/CD Tracer instruments existing CI pipelines to collect SDLC metadata without workflow YAML changes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs-lunar.earthly.dev/release-notes/cli/2025.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.