lakeFS Enterprise v1.93.0¶

Changelog¶

What's new:¶

Datasets: support creating and editing datasets through pull requests, enabling review workflows for dataset changes
Datasets: the dataset form now suggests a source path based on the data item being added
WebUI: custom object viewers can now render binary content and use range reads for large objects
Performance: zero-copy read/write optimizations reduce memory overhead for block storage operations

Bugs Fixed:¶

Fixed a bug where deleting a repository could leave behind unreleased storage
Audit Log Redaction: each field is now truncated independently instead of truncating the combined log entry

Assets¶

`checksums.txt`		1.8 kB	2026-07-30
`lakefs-enterprise_1.93.0_Darwin_arm64.tar.gz`	`sha256:6332036aa414226688289d2d559f11b967087c1096e29f68b437abd42dc31324`	74.4 MB	2026-07-30
`lakefs-enterprise_1.93.0_Darwin_x86_64.tar.gz`	`sha256:f92bec19450b1e5e4833cf525e2e79f8d127eba8d05b37ab5935593fb68fbf42`	79.8 MB	2026-07-30
`lakefs-enterprise_1.93.0_Linux_arm64.tar.gz`	`sha256:c551ed2ac1c26bff4c27b59dc400d17c2d94ad5089c747c71f91367ca24514ae`	70.9 MB	2026-07-30
`lakefs-enterprise_1.93.0_Linux_x86_64.tar.gz`	`sha256:8a620cce19c1711f8edbfa75395ef9643bbd63845bbe92339f3934a7db7b4b3f`	78.3 MB	2026-07-30
`lakefs-enterprise_1.93.0_Windows_arm64.zip`	`sha256:c1d71a90ebd079f73cdcb49c28f40def2dc7b6676d7d68a28696e105df4fa71b`	71.2 MB	2026-07-30
`lakefs-enterprise_1.93.0_Windows_x86_64.zip`	`sha256:94c4d47076337d083a845337e36ff49bfd789b960d268164bd92001b41148792`	79.9 MB	2026-07-30

Docker¶

docker pull treeverse/lakefs-enterprise:1.93.0

Verify the signature (optional)¶

Requires Cosign:

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