v0.83.4

Changelog

What's new:

• Deprecate lakefs import (#4323)
• Added download capability to lakectl (#4418)

Bug fixes:

• Fix README.md file viewer not displaying content according to file extension (#4380)
• Fix entity creation fails when % is used in entity name (#4414)
• Fix lakeFS returns code 500 when getting absent object (#4427)
• Fix blank page when viewing objects in subdirectories (#4449)

v0.83.3

What's new:

• lakectl autocomplete with repository name (#4320)
• Flush statistics based on events size (#4347)
• lakectl check bad response (#4331)

Bug fixes:

• Update and create policy use the user's provided ID (#4359)
• Fix KV local path using tilde (~) doesn't expand (#4330)
• Fix username not shown for OIDC users (#4324)
• Fix create repository API should return status created (#4336)
• Correctly prefix "after" params in lakeFS auth service (#4353)
• Fix create policy API and descriptor to return Conflict status (#4350)
• Fix: Auth update policy (#4355)

v0.80.2

Upgrade Notes:
This release requires running database migration.
The lakeFS service will not run if the migration version isn't compatible with the binary.
Before running the new version you will be required to run migrate, with the new version.
Please refer to this upgrade documentation for more information on the specific migration to KV.

This is the first lakeFS version over Key-Value Store
lakeFS is decoupling from PostgreSQL and moving to a KV Store interface.
This will provide greater flexibility and allow production groups working with lakeFS to select their backing DB of choice.
Check our updated Deploy lakeFS page, for deployment instructions.
Also make sure to check our Sizing Guide for best practices, requirements and benchmarks

Changelog

• 38836a9 Fix multiparts KV migration for null content-type (#4343)

v0.83.2

Changelog

What's new:

• Adding lakeSF description to python's pypi package (#4260)
• Report extended information with metrics (off by default) (#4196)

Bug fixes:

• Fix S3 gateway delete object limits check (#4240)
• Fix S3 gateway report status code and operation ID in case of an error (#4293)
• Fix UI render error inside repo error (#4301)
• Fix UI repository settings label width (#4300)
• Fix logging.IsTracing should check default logger level (#4252)

v0.82.0

Changelog

What's new:

• UI: New file viewer (#4226)
• Performance improvements: enable delete-objects as part of Graveler (#4205)

Bug fixes:

• Migrate work as part of setup for auth-api installations (#4208)
• Invite user is enabled when SMTP server is not configured (#4224)

0.81.1

Changelog

• 6b0bbb5 Fix local settings command (#4200)

0.81.0

What's new:

• Run standalone lakeFS (no PostgreSQL!) with Badger KV for experimentation purposes.
• Add delete operation for GC rules (#4143)
• Support AWS named profile for dynamodb (#4163)
• Add pgxpool metrics to kv/postgres implementation (#4137)

Bug fixes:

• Fix: Pyramid delete before open (#4062)

v0.80.1

Update: Please upgrade using v0.80.2 release

Changelog

Upgrade Notes:
This release requires running database migration.
The lakeFS service will not run if the migration version isn't compatible with the binary.
Before running the new version you will be required to run migrate, with the new version.
Please refer to this upgrade documentation for more information on the specific migration to KV.

This is the first lakeFS version over Key-Value Store
lakeFS is decoupling from PostgreSQL and moving to a KV Store interface.
This will provide greater flexibility and allow production groups working with lakeFS to select their backing DB of choice.
Check our updated Deploy lakeFS page, for deployment instructions.
Also make sure to check our Sizing Guide for best practices, requirements and benchmarks

Bug fix:

• Fix PartitionIterator panic on Close (#4108)
• UI: Fix error while conflicting diff of binary objects, show original file size (#4105)

What's new:

• Dockerfile update CA certificates (#4101)

v0.80.0

Changelog

Update: Please upgrade using v0.80.2 release

Upgrade Notes:
This release requires running database migration.
The lakeFS service will not run if the migration version isn't compatible with the binary.
Before running the new version you will be required to run migrate, with the new version.
Please refer to this upgrade documentation for more information on the specific migration to KV.

This is the first lakeFS version over Key-Value Store
lakeFS is decoupling from PostgreSQL and moving to a KV Store interface.
This will provide greater flexibility and allow production groups working with lakeFS to select their backing DB of choice.
Check our updated Deploy lakeFS page, for deployment instructions.
Also make sure to check our Sizing Guide for best practices, requirements and benchmarks

v0.70.6

Changelog

• UI: fix focus on branch lookup while creating tag (#4005)