lakeFS Enterprise v1.95.0¶

Changelog¶

What's new:¶

Private preview: Multi tenants support
S3 blockstore: a custom STS endpoint can now be set with blockstore.s3.sts_endpoint, so S3-compatible deployments serving STS at their own address can use Iceberg credential vending without relying on the AWS_ENDPOINT_URL_STS environment variable
Azure blockstore: a specific user-assigned managed identity can now be selected with blockstore.azure.managed_identity_client_id, for hosts with more than one identity attached

Bugs Fixed:¶

Security fixes
Iceberg REST Catalog: the table metadata log is now trimmed on commit, capping its growth across many commits

Assets¶

`checksums.txt`		1.8 kB	2026-08-07
`lakefs-enterprise_1.95.0_Darwin_arm64.tar.gz`	`sha256:f38b9b038f64238bc1342ba55d0095050f116023f1be5eca71619e26ab4bc98a`	74.5 MB	2026-08-07
`lakefs-enterprise_1.95.0_Darwin_x86_64.tar.gz`	`sha256:a142106834cfa127dc5845c92e695ddeda84d4b59defac943b68a675e1cdbc46`	79.9 MB	2026-08-07
`lakefs-enterprise_1.95.0_Linux_arm64.tar.gz`	`sha256:428a1ad7923ac67083cd5c3c91c510e9e0ac93e604523c9cc579c9a4c4c60dba`	71.0 MB	2026-08-07
`lakefs-enterprise_1.95.0_Linux_x86_64.tar.gz`	`sha256:4128ff49f7da695e7ad5f715b6c0c00fdc2c50fb22188ba7a1ed10ccc42585c8`	78.4 MB	2026-08-07
`lakefs-enterprise_1.95.0_Windows_arm64.zip`	`sha256:477c78467315702c1322b769b4d63bb3cd0c60652db12a277bfff6dbddec19d6`	71.3 MB	2026-08-07
`lakefs-enterprise_1.95.0_Windows_x86_64.zip`	`sha256:5eb1c87655a1bd96a29a2ddeb9c7af93efb19fe63abac8a9e0928b267feec3db`	80.0 MB	2026-08-07

Docker¶

docker pull treeverse/lakefs-enterprise:1.95.0

Verify the signature (optional)¶

Requires Cosign:

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