Lakefs

Latest version: v0.7.1

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

Scan your dependencies

Page 21 of 30

0.53.0

- Add support for LDAP authentication (2058).
- Support object content-type and user metadata (2296).
- Support multiple commits in lakectl revert (2345).
- `lakectl diff`: support two way diff.
- `lakectl diff`: allow including uncommitted changes in the diff.
- Fix Trino AVRO format access via S3 gateway (2429).
- Support lakectl fs rm --recursive (2446).
- Fix UI list users pagination (2581).
- Add tree-view for uncommitted, compare and commit views (2174)

0.52.2

- Fix nil panic for missing configuration of Airflow hook (2533)
- Allow more characters and different length of key/secret for user authorizations (2501)
- Fix nil panic for missing configuration of Airflow hook (2533)
- Fix failed to merge branch running on Windows locally - access is denied (2531)
- Fix UI failed to load on Windows - invalid mime type (2537)
- Fix UI path reset on branch change bug in object view (2441)
- Fix UI changing the base-branch changes the compared-branch bug (2440)

0.52.0

- Protected Branches (2181): define rules to prevent direct changes on some of your branches.
Only merges are allowed into protected branches.
Combine these with pre-merge hooks to validate your data before it is on your production branches.
- Fix filter dialog unsearchable bug (2460)
- Fix s3 multipart upload location url (1779)

0.51.0

- Add new "AttachStorageNamespace" IAM action. Controls users' ability to
create repositories with particular storage namespaces (bucket names).
(2220)
- Fix path encoding when checking sigV2 signatures in the S3 gateway.
- [S3 gateway] Return HTTP 409 (Conflict) when creating existing repo (2451)

0.50.0

- Fix double slash bug in storage namespace (2397)

0.49.0

- Add search locations to load lakeFS configuration. More information on
https://docs.lakefs.io/reference/configuration (#2355)
- Fix ARNs parsing confusion when the account-ID field contained a slash or
the resource-ID a colon. Configurations (incorrectly) using a slash "`/`"
to separate account from resource in the ARN will need to switch to use a
colon "`:`". However such configurations are probably incorrect, as
lakeFS does not currently set account fields. And configurations using
resources containing a colon will now work correctly.

Page 21 of 30

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.