lakeFS Enterprise v1.100.0¶

Changelog¶

What's new:¶

Branch compaction: optionally compact a branch’s staging area to improve efficiency as changes accumulate. Compaction does not affect repository data and is disabled by default
Actions: Enhance control over hook network access by restricting requests to specific IP addresses or CIDR ranges using the actions.network.blocked_addresses configuration.
lakectl: new commands for managing tenant user and group membership

Bugs Fixed:¶

S3 gateway: listing a path under a branch, tag or commit that does not exist returned an error instead of an empty listing
Web UI: users without access to the default branch will fall back to the first branch that has access

Assets¶

`checksums.txt`		1.8 kB	2026-09-08
`lakefs-enterprise_1.100.0_Darwin_arm64.tar.gz`	`sha256:df147cd9e05f2d50653014fcd9d0c8367ff59460531e2c852d23ec3124b22d3f`	74.6 MB	2026-09-08
`lakefs-enterprise_1.100.0_Darwin_x86_64.tar.gz`	`sha256:ca450ce75cf593ee785e338681c646eebcf97613ad2080d835e7407f5011ec96`	80.2 MB	2026-09-08
`lakefs-enterprise_1.100.0_Linux_arm64.tar.gz`	`sha256:36809b9c8fdefeab02b477257c85102478744ca2f01e85a71768ace02bad7361`	71.1 MB	2026-09-08
`lakefs-enterprise_1.100.0_Linux_x86_64.tar.gz`	`sha256:dd700a019a2b522fe178e82cc74d56334557f984ced0b7cd5b9627e3c317bf70`	78.6 MB	2026-09-08
`lakefs-enterprise_1.100.0_Windows_arm64.zip`	`sha256:c41fb255a8b7c8fd4f058c195e674b14f7517859f866fef5b5863ad2c4c0e7d5`	71.4 MB	2026-09-08
`lakefs-enterprise_1.100.0_Windows_x86_64.zip`	`sha256:a9f5e69ac0eba7c14f3a0c49cd423c46193b295f37f9a333762d6e55462d4de5`	80.2 MB	2026-09-08

Docker¶

docker pull treeverse/lakefs-enterprise:1.100.0

Verify the signature (optional)¶

Requires Cosign:

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