lakeFS Enterprise v1.88.0¶

Changelog¶

What's new:

Pull request comments are now supported — users can comment on pull requests, with resolver attribution and write-permission checks
Branch creation and update time are now exposed via the API, UI, and lakectl, with default dates backfilled for branches
Fix Lua hooks capturing client IP for IP-restricted auth
Web UI Lua syntax highlighting is now available in the file editor
Communication preferences step removed from lakefs setup
Introducing datasets management via API

Bugs Fixed:

Fixed async hooks running against cancelled request contexts

Assets¶

`checksums.txt`		1.8 kB	2026-06-25
`lakefs-enterprise_1.88.0_Darwin_arm64.tar.gz`	`sha256:6922c7dd652c9370af9ab23d5ce5e4c74cc2d4bf5484c1e8d7fde02f471e1e2b`	73.4 MB	2026-06-25
`lakefs-enterprise_1.88.0_Darwin_x86_64.tar.gz`	`sha256:6b606c275f9f88817a6d6a770c2dafee931a0f453c50e4a708acc9704b0c3dbf`	78.6 MB	2026-06-25
`lakefs-enterprise_1.88.0_Linux_arm64.tar.gz`	`sha256:32fb9bec1c547485973c08785b4b6fd4aa9f77c59777feb9109175e25a56a086`	69.9 MB	2026-06-25
`lakefs-enterprise_1.88.0_Linux_x86_64.tar.gz`	`sha256:46a087b8722d065e763e6e17342dbafdab827473c9ddf38396f8978616f4384c`	77.1 MB	2026-06-25
`lakefs-enterprise_1.88.0_Windows_arm64.zip`	`sha256:81d951a49f77aaaafb6ea37b30d24b39ab16017fb18a3d346fe953026af2f248`	70.2 MB	2026-06-25
`lakefs-enterprise_1.88.0_Windows_x86_64.zip`	`sha256:7cff0b74d3eef50e9943fb1615cc2947b5555173db7956d6ed444ef22f0a5bce`	78.7 MB	2026-06-25

Docker¶

docker pull treeverse/lakefs-enterprise:1.88.0

Verify the signature (optional)¶

Requires Cosign:

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