Skip to content

lakeFS Enterprise v1.90.0

Changelog

🆕 What's new:

  • Added support for Iceberg tables with local storage
  • Added object-level ABAC, allowing policy conditions based on object metadata
  • Admins can now restrict which authentication methods are enabled via configuration
  • Added IP-based redaction for audit logs
  • Improved internal object lifecycle and caching for better performance and reliability

🐛 Bugs Fixed:

  • Fixed S3 gateway to properly lowercase and validate user-metadata keys
  • Fixed copy requests exceeding the S3 copy size limit to correctly return a 400 error instead of failing unexpectedly

Assets

checksums.txt1.8 kB2026-07-09
lakefs-enterprise_1.90.0_Darwin_arm64.tar.gzsha256:342fda0948c0e5b3207572e6f7386e50bf5f95abd06dc59c74ce91ed5cbe054c74.2 MB2026-07-09
lakefs-enterprise_1.90.0_Darwin_x86_64.tar.gzsha256:6ba8d07561ec3332b7aa663fb0cce852ba85f33a08932824f102ca8567870c6579.6 MB2026-07-09
lakefs-enterprise_1.90.0_Linux_arm64.tar.gzsha256:5c243904fe7f9ac978f3543f86a0112c08a0b4be97beb834c4649460821ec7b770.7 MB2026-07-09
lakefs-enterprise_1.90.0_Linux_x86_64.tar.gzsha256:80100025ff29811275c1e96aac7905c4db71cf70fa3145e8d8d98b82a8e0d30a78.1 MB2026-07-09
lakefs-enterprise_1.90.0_Windows_arm64.zipsha256:625a238b9304affd91055ff3d91e302044a757bf241eeeb439660320cff49f8271.0 MB2026-07-09
lakefs-enterprise_1.90.0_Windows_x86_64.zipsha256:c4f6672dcf09e83399f45926dda9f13cb5586437e5c1f7692cf7727b7227a8f179.7 MB2026-07-09

Docker

docker pull treeverse/lakefs-enterprise:1.90.0

Verify the signature (optional)

Requires Cosign:

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