Edgy

Latest version: v0.29.0

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

Scan your dependencies

Page 1 of 10

0.29.0

Added

- Convert for most fields defaults to server_default to ease migrations. There are some exceptions.
- Add the setting `allow_auto_compute_server_defaults` which allows to disable the automatic generation of server defaults.
- `pre_migrate` and `post_migrate` signals.

Changed

- `get_default_value` is now also overwritable by factories.
- The undocumented default of `BooleanField` of `False` is removed.
- The signal receiver functions receive more parameters.

Fixed

- JSONField `default` is deepcopied to prevent accidental modifications of the default.
There is no need anymore to provide a lambda.
- `pre_update` and `post_update` is not called anymore when calling save and the update path is executed.
- `apply_default_force_nullable_fields` could run into transaction problems.
- `bulk_update` and `bulk_create` optimizations and small fixes.
- `pre_update` and `post_update` are now received when using a QuerySet.
- Allow prefixing column names in CompositeField via `prefix_column_name` parameter.

Breaking

- The undocumented default of `BooleanField` of `False` is removed.
- Fields compute now `server_default`s for a set default. This can be turned off via the `allow_auto_compute_server_defaults` setting.

0.28.2

Fixed

- Missing `message` parameter passing in migrate command after refactory.

0.28.1

Changed

- `hash_names` has now two prefix parameters: `inner_prefix`, `outer_prefix`.

Fixed

- `hash_names` with unique_together incorrectly fed the `uc` prefix into the hasher. This makes the names unidentificatable.
- `BooleanField` logic for automatic migrations works by using server_default.

0.28.0

Added

- `null-field` or `nf` parameter for makemigrations/revision.
- Add `FORCE_FIELDS_NULLABLE` ContextVar.
- Add `CURRENT_FIELD_CONTEXT` ContextVar.
- Add automigrations (migrations capsuled in Registry).

Changed

- The default migration templates allow now to use complex defaults for migrations.
- Fields must use get_columns_nullable instead of ColumnDefinitionModel null. for determining if the columns should be nullable.
- For model `save` and `update` the values can be callables which are evaluated.
- Streamline ContentTypeField in using a parameter-less default function. Use `CURRENT_FIELD_CONTEXT` ContextVar field for referencing the owner.
- Fail when specifying a server_default for ForeignKey, ManyToMany, FileField, ImageField. This is not possible.
- Internals: _insert and _update have now a different signature.

Fixed

- ForeignKeys aren't required to be saved models when passed.
- Cli command revision takes now also the arg argument.
- Revisioning works now with relative revisions with - (e.g. -2).
- Downgrades are now possible with unique_together. Build a constraint name from the fields.
- `is_partial` was incorrectly set to always `False` for the model.save update path.
- FileFields could have make problems when migrating.
- Differing ruff versions and rules between `hatch fmt` and `pre-commit`.

0.27.3

Added

- `bulk_get_or_create` to queryset allowing to bulk inserting or getting existing objects.

Fixed

- BooleanField typing. Thanks to Izcarmt95.

0.27.2

Chamged

- Edgy now allows inheritance of `unique_together` and `indexes` from abstract classes.

Fixed

- Typo in `BaseContentTypeField` from `BaseContentTypeFieldField`.

Page 1 of 10

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.