Releases: kitware-resonant/django-s3-file-field
Releases · kitware-resonant/django-s3-file-field
v1.0.1
v1.0.0
Breaking Changes
- The package extra
boto3
has been renamed tos3
.- Change dependencies from
django-s3-file-field[boto3]
->django-s3-file-field[s3]>=1
- Change dependencies from
- The Python client
S3FileFieldClient.upload_file
function signature has changed.- All arguments must be be passed as keywords.
- A
file_content_type
argument is now requirerd. - See the usage example for details.
Potentially Incompatible Changes
- Supported Python versions are now:
3.8
3.9
3.10
3.11
3.12
- Supported Django versions are now:
3.2
4.1
4.2
django-storages
>=1.14
is now required.django-minio-storage
>=0.5
is now required.
New Features
- Uploads should now generally set
Content-Type
metadata on the stored object. - Improved timeouts for failed HTTP connections.
- New versions of Django and Python are supported.
- Re-defining an existing
S3FileField
-containingModel
is now permitted.- A warning will still be emitted, as redefinition is not necessarily safe.
- This will allow compatibility with hot-reloading (e.g. IPython autoreload).
- Internal bug fixes and build tooling improvements.
v0.3.2
- Add support for Django 4.2, drop support for Django 3.0, 3.1
- Add
py.typed
file for Python client
v0.3.1
- Add a
py.typed
file - Add type hints and harden validation of
S3FileSerializerField
v0.3.0
- Add support for Django 4.0
- Add support for Python 3.10
v0.2.0
- Add pytest fixtures for external use
- Remove
S3FileFieldTestClient
- Update Python client usage documentation to prevent file mode bugs
- Fix the Python client return value of
S3FileFieldClient.upload_file
- Improve validation of
field_id
v0.1.2
v0.1.1
- Add a readme for the Javascript client
v0.1.0
- Refactored the entire external API of the Javascript client
- Allow the Javascript client to take a configuration for API requests
- Ensure that uploads from the server-rendered widget are authenticated
- Ensure that migrations don't contain default kwargs
- Fix a bug where the widget's CSS was not included in form assets
v0.0.23
Fix published releases.