lakeFS Enterprise v1.107.0¶

Changelog¶

What's new:¶

API: New endpoints let clients run S3 multipart uploads fully client-side using requests signed by lakeFS
lakectl: fs upload and local commit can use S3 multipart uploads fully from the client-side when supported

Bugs Fixed:¶

Auth: Requests with an empty access key now return HTTP 401
KV (CosmosDB): New containers are now created with partition key V2
Retried conditional writes no longer fail when a commit lands on the branch mid-write in case of identical update

Assets¶

`checksums.txt`		1.8 kB	2026-10-20
`lakefs-enterprise_1.107.0_Darwin_arm64.tar.gz`	`sha256:c26d785a11d53759e305758eda0e1f6a95fb1cbd0f6898f71f42a842b2596b39`	76.9 MB	2026-10-20
`lakefs-enterprise_1.107.0_Darwin_x86_64.tar.gz`	`sha256:1c1e9205c47debe8d4615109522907c731fb74999a3a61f0e83b95b712733691`	82.4 MB	2026-10-20
`lakefs-enterprise_1.107.0_Linux_arm64.tar.gz`	`sha256:cc2ab32b64722b00758552a0c983fd22f40d1b4165032ff8164e0a54f5ad9504`	73.3 MB	2026-10-20
`lakefs-enterprise_1.107.0_Linux_x86_64.tar.gz`	`sha256:1efe720def5b41c10a15ce4b470f1ff84c5b66c11ec970a10db40053b8d56698`	80.7 MB	2026-10-20
`lakefs-enterprise_1.107.0_Windows_arm64.zip`	`sha256:5bfe93b7282711489697fcfa0a3cf9dd091986c86e2cf0b3165c428ddcd020dd`	73.5 MB	2026-10-20
`lakefs-enterprise_1.107.0_Windows_x86_64.zip`	`sha256:c13081315c90c389b9a8f3b53eb8d9937079c95cbd692f19a341720320fff958`	82.4 MB	2026-10-20

Docker¶

docker pull treeverse/lakefs-enterprise:1.107.0

Verify the signature (optional)¶

Requires Cosign:

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