lakeFS Enterprise v1.89.0¶

Changelog¶

What's new:

S3 gateway: auth-layer rejections now emit audit records with a request ID; auth-API fetch failures are retryable 500s instead of silent AccessDenied; principals with only fs:ListObjects can perform the empty-prefix bucket probe without revealing branch names
Iceberg Catalog: remove-snapshots table commits now also remove associated logs, statistics, and refs
Datasets: UI for datasets management

Bugs Fixed:

Delta exporter: fixed a path-prefix bug that caused tables to be incorrectly re-exported when another table's path starts with the same string
Dataset Data Access: Fixed an issue that prevented clients from reading dataset data.

Assets¶

`checksums.txt`		1.8 kB	2026-07-01
`lakefs-enterprise_1.89.0_Darwin_arm64.tar.gz`	`sha256:78156028b514f3af4709771904018484459d15ee851af4e2481cd027d3f4b15e`	74.2 MB	2026-07-01
`lakefs-enterprise_1.89.0_Darwin_x86_64.tar.gz`	`sha256:84d15824b237aef70f380f84592effab3c506e167bbb9ec33eac5c948868ade5`	79.6 MB	2026-07-01
`lakefs-enterprise_1.89.0_Linux_arm64.tar.gz`	`sha256:641005a4dc7d320286c90c47936e688088c218f938c6b0fd6ba809e1fdb1436f`	70.6 MB	2026-07-01
`lakefs-enterprise_1.89.0_Linux_x86_64.tar.gz`	`sha256:d8d87d9c5fde044d40448c7b859b09b1ad278b2cd5a7fbe3239b8d0df0334f57`	78.0 MB	2026-07-01
`lakefs-enterprise_1.89.0_Windows_arm64.zip`	`sha256:7a26afd744b479343d9b63e20fe97ceac4320c9496fc1af7cb69a0fd98a62cad`	71.0 MB	2026-07-01
`lakefs-enterprise_1.89.0_Windows_x86_64.zip`	`sha256:f256a2f4be09434e928192c861743124edc43b4e5ffc96d6993795f3c617d6ce`	79.6 MB	2026-07-01

Docker¶

docker pull treeverse/lakefs-enterprise:1.89.0

Verify the signature (optional)¶

Requires Cosign:

cosign verify treeverse/lakefs-enterprise:1.89.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.89.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