lakeFS Enterprise v1.87.0¶

Changelog¶

What's new:

OIDC/SAML: populate a new user's email from a configurable claim (email_claim_name) at creation time
Pull requests: API support for comments
Iceberg REST Catalog: repo-scoped (relative_to/{repo}) config returns the repository storage namespace as default-base-location
lakectl local commit: honor the --yes flag to bypass the confirmation prompt shown after an interrupted local operation
Deprecate Iceberg push/pull

Bugs Fixed:

Fix: branch lifecycle policies reject max_age/max_inactivity_time over 10 years, so a value mistakenly entered in seconds is no longer stored as a multi-thousand-year threshold that never matches

Assets¶

`checksums.txt`		1.8 kB	2026-06-18
`lakefs-enterprise_1.87.0_Darwin_arm64.tar.gz`	`sha256:322f35f817ea93e4df342ee5e52df6a6389b902984a6cbf45722294f8b114113`	74.6 MB	2026-06-18
`lakefs-enterprise_1.87.0_Darwin_x86_64.tar.gz`	`sha256:93312d3638d732611d0b92c749ae179d5e4f3c168dd272c0dc1b3dfe333d1abd`	79.8 MB	2026-06-18
`lakefs-enterprise_1.87.0_Linux_arm64.tar.gz`	`sha256:290b9c48d2c3a35fc9acbdb3ee75989b85bcc3e4798b1ba5bbeeee113b85b9cc`	71.0 MB	2026-06-18
`lakefs-enterprise_1.87.0_Linux_x86_64.tar.gz`	`sha256:11fb8d3d0c0555b9c9c4ea51b6b93d923d917f8801f07699be9a0ffadaeeb5d6`	78.1 MB	2026-06-18
`lakefs-enterprise_1.87.0_Windows_arm64.zip`	`sha256:0256f5872f4040164bb520836e1a494dda816ddfc740463de53dd46e0f189229`	71.3 MB	2026-06-18
`lakefs-enterprise_1.87.0_Windows_x86_64.zip`	`sha256:37d27f760107899edd2446eec60b0d2bf150cc267146ba1e0a0dd51050e9691d`	79.7 MB	2026-06-18

Docker¶

docker pull treeverse/lakefs-enterprise:1.87.0

Verify the signature (optional)¶

Requires Cosign:

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