[noissue]: Update django-import-export requirement from ~=2.5.0 to ~=3.0.1

[dependabot]

Updates the requirements on django-import-export to permit the latest version.

Changelog

Sourced from django-import-export's changelog.

3.0.1 (2022-10-18)

• Updated django-import-export-ci.yml to fix node.js deprecation
• bugfix: DateTimeWidget.clean() handles tz aware datetime (#1499)
• Updated translations for v3.0.0 release (#1500)

3.0.0 (2022-10-18)

Breaking changes ################

This release makes some minor changes to the public API. If you have overridden any methods from the resources or widgets modules, you may need to update your implementation to accommodate these changes.

• Check value of ManyToManyField in skip_row() (#1271)

  • This fixes an issue where ManyToMany fields are not checked correctly in skip_row(). This means that skip_row() now takes row as a mandatory arg. If you have overridden skip_row() in your own implementation, you will need to add row as an arg.

• Bug fix: validation errors were being ignored when skip_unchanged is set (#1378)

  • If you have overridden skip_row() you can choose whether or not to skip rows if validation errors are present. The default behavior is to not to skip rows if there are validation errors during import.

• Use 'create' flag instead of instance.pk (#1362)

  • import_export.resources.save_instance() now takes an additional mandatory argument: is_create. If you have overridden save_instance() in your own code, you will need to add this new argument.

• widgets: Unused *args params have been removed from method definitions. (#1413)

  • If you have overridden clean() then you should update your method definition to reflect this change.
  • widgets.ForeignKeyWidget / widgets.ManyToManyWidget: The unused *args param has been removed from __init__(). If you have overridden ForeignKeyWidget or ManyToManyWidget you may need to update your implementation to reflect this change.

• Admin interface: Modified handling of import errors (#1306)

  • Exceptions raised during the import process are now presented as form errors, instead of being wrapped in a <H1> tag in the response. If you have any custom logic which uses the error written directly into the response, then this may need to be changed.

• ImportForm: improve compatibility with previous signature (#1434)

  • Previous ImportForm implementation was based on Django's forms.Form, if you have any custom ImportForm you now need to inherit from import_export.forms.ImportExportFormBase.

• Allow custom change_list_template in admin views using mixins (#1483)

  • If you are using admin mixins from this library in conjunction with code that overrides change_list_template (typically admin mixins from other libraries such as django-admin-sortable2 or reversion), object tools in the admin change list views may render differently now.

• import.html: Added blocks to import template (#1488)

  • If you have made customizations to the import template then you may need to refactor these after the addition of block declarations.

Deprecations ############

This release adds some deprecations which will be removed in a future release.

• Add support for multiple resources in ModelAdmin. (#1223)

  • The *Mixin.resource_class accepting single resource has been deprecated and the new *Mixin.resource_classes accepting subscriptable type (list, tuple, ...) has been added.
  • Same applies to all of the get_resource_class, get_import_resource_class and get_export_resource_class methods.

• Deprecated exceptions.py (#1372)

... (truncated)

Commits

• 639654a Preparing release 3.0.1
• 360b58c updated ci.yml to fix node.js deprecation
• 683889a bugfix: DateTimeWidget.clean() handles tz aware datetime (#1499)
• 870b1c7 Updated translations for release 3.0 (#1500)
• 69b538d Update German translation (#1498)
• 0589f18 Back to development: 3.0.1
• 5319a6b Preparing release 3.0.0
• 70bb967 documentation formatting fix
• 37c2618 removed temp release 3 config / comment
• 63c1bef squashed changes from release-3-x
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #64.