lakeFS Enterprise v1.108.0¶

Changelog¶

Important note: the auth.ui_config.rbac setting is deprecated and will be removed in a future release. lakeFS logs a warning at startup when it is set to none or simplified; set it to internal, or remove it to use the default.

What's new:¶

Iceberg Catalog: system is a reserved repository name, and catalog writes under it return 406

Bugs Fixed:¶

Security: Enhanced connection security by blocking TLS certificates tied to the eMudhra CA compromise (CVE-2026-111943).
API: The branch lifecycle policies ETag is now quoted, so lifecycle edits keep working behind proxies that drop unquoted ETags; If-Match accepts both forms

Assets¶

`checksums.txt`		1.8 kB	2026-10-21
`lakefs-enterprise_1.108.0_Darwin_arm64.tar.gz`	`sha256:ec53b41fb482217f6b546c970e55796669e8d01bd2af2823b83186a25af90af7`	77.0 MB	2026-10-21
`lakefs-enterprise_1.108.0_Darwin_x86_64.tar.gz`	`sha256:82a9cb539adb2eaef3e4fc34344c01527477553ea04d01e050ec05ab23aea008`	82.4 MB	2026-10-21
`lakefs-enterprise_1.108.0_Linux_arm64.tar.gz`	`sha256:f3243f2c6f8f2fecd832fab3c63c8ff5165956b5f32170dfa61ebe43a4e46bff`	73.3 MB	2026-10-21
`lakefs-enterprise_1.108.0_Linux_x86_64.tar.gz`	`sha256:48e5a218044fb5d4923e3791e64fbc2fee5aac1e97557f93bb1ca6580c9421fa`	80.8 MB	2026-10-21
`lakefs-enterprise_1.108.0_Windows_arm64.zip`	`sha256:12bc5c1fdde77b206b94938357637955f9ebb708af0c87788c720849ad5dd97c`	73.6 MB	2026-10-21
`lakefs-enterprise_1.108.0_Windows_x86_64.zip`	`sha256:4963a1c3f1ccf5a11e3c457369fcd9016ba56c5a2af613b133adb96f550fd8d5`	82.5 MB	2026-10-21

Docker¶

docker pull treeverse/lakefs-enterprise:1.108.0

Verify the signature (optional)¶

Requires Cosign:

cosign verify treeverse/lakefs-enterprise:1.108.0 \
    --certificate-identity-regexp='^https://github\.com/treeverse/lakeFS\-Enterprise/\.github/workflows/' \
    --certificate-oidc-issuer='https://token.actions.githubusercontent.com'

Expected output

Verification for index.docker.io/treeverse/lakefs-enterprise:1.108.0 --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - The code-signing certificate was verified using trusted certificate authority certificates