Lakefs

Latest version: v0.6.2

Safety actively analyzes 639107 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 15 of 29

0.80.0

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](https://docs.lakefs.io/reference/upgrade.html#lakefs-0800-or-greater-kv-migration) 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](https://docs.lakefs.io/deploy/#deploy-lakefs) page, for deployment instructions.
Also make sure to check our [Sizing Guide](https://docs.lakefs.io/understand/sizing-guide.html#lakefs-kv-store) for best practices, requirements and benchmarks

0.70.6

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

0.70.5

Bug fix:
- Fix panic in commit under KV, with nil tombstone (3976)

0.70.4

What's new:
- Improve commit log performance for single match by adding limit flag (3970)
- Change Histogram buckets to better fit lakeFS commands (3902)

0.70.3

What's new:
- Improve commit log performance (3936)

0.70.2

What's new:
- Improve 'commit log by objects' performance (3920)

Page 15 of 29

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.