Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [v1.5.2] - 2026-07-08

Multi-arch container image on GHCR, fuzz hardening, and CLI help-text polish.

### Added
- Multi-arch container image published to
`ghcr.io/deveshctl/layerx` on every tagged release (linux/amd64 +
Expand All @@ -24,7 +28,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
crasher reproducer. The nightly fuzz workflow retains its longer
budgets and is unchanged.

### Fixed
### Fixed
- Accept all standard truthy values for the `CI` environment variable
(`true`, `True`, `TRUE`, `1`, `yes`), not only the exact lowercase
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -154,15 +154,15 @@ sudo rpm -i layerx_linux_arm64.rpm

### Direct download

Prebuilt binaries for Linux, macOS, and Windows (amd64 + arm64) on the [Releases page](https://github.com/deveshctl/layerx/releases). Replace `latest` with a specific tag (e.g. `v1.5.1`) in any URL above.
Prebuilt binaries for Linux, macOS, and Windows (amd64 + arm64) on the [Releases page](https://github.com/deveshctl/layerx/releases). Replace `latest` with a specific tag (e.g. `v1.5.2`) in any URL above.

### Container image (Docker, Podman, any OCI runtime)

Every tagged release also publishes a multi-arch image (linux/amd64 + linux/arm64) to GitHub Container Registry:

```
ghcr.io/deveshctl/layerx:latest
ghcr.io/deveshctl/layerx:v1.5.1 # pin a specific version
ghcr.io/deveshctl/layerx:v1.5.2 # pin a specific version
```

LayerX is a client to a running container engine, so the image needs the host engine's socket bind-mounted in. It cannot inspect live images without one — but archive mode (bind-mount a `docker save` / OCI tar) works without any socket at all.
Expand Down
Loading