Placeholder to keep track of what needs to be removed/changed in this major release

• Rename LOG_REQUESTS to LOG_OUTGOING_REQUESTS (change in OAF? or override locally? https://github.com/maykinmedia/open-api-framework/blob/f54907d65adfaa5dd6fd2bdaa634bbacb8b457d0/open_api_framework/conf/base.py#L552) and rename ENABLE_STRUCTLOG_REQUESTS to LOG_REQUESTS
• Use CELERY_BROKER_URL envvar for CELERY_BROKER_URL setting (currently uses CELERY_RESULT_BACKEND as per OAF https://github.com/maykinmedia/open-api-framework/blob/a9eb1d76f22c6b3fddf4969cd30bcf7783cd1f1a/open_api_framework/conf/base.py#L1285)
• Remove deprecated views for OpenAPI specs (#2189) (DeprecationRedirectView)
• See if any upgrade check constraints need to be added
• Remove django.contrib.sites and related config step
  • check register_kanalen
• use new exception_handler from commonground-api-common (which updates error format to be application/problem+json compliant)
• other setupconfig changes?
• TODO check more deprecations and XXX: ... comments
• Rename to Open Object
• Squash migrations (?)
• Should we release API v3 as well? maybe a separate issue to define a v3 for the API
  • then we could deprecate data_attr
  • data_icontains simplify to use _icontains and add separate regex search query param?

Release checklist

• Resolve release blockers
  • ⚡ [maykinmedia/open-api-framework#211] Optimize memory usage (max-requests, flower) #741
  • 📝 [#564] refactor docs for objecttype migrations #737
  • 🚚 [#747] Use maykinmedia/open-object repo for github and dockerhub #755
• Upgrade open-api-framework to latest version
• Check security tab and upgrade packages to fix vulnerabilities
• Check translations
• Bump API version number (if applicable)
  • Version bump
  • Regenerate API spec
  • Update READMEs with release dates + links
• Bump version number with bin/bump-my-version.sh bump <major|minor|patch>
• Update changelog (check how OF lists breaking changes)
  • Add changelog entry + warning for Objecttypes migration
    • mention that Objects now ignores the domain of the objecttype and only checks the path, meaning that doing POST with URL reference to the external objecttypes API still work (but will use the internal objecttype with that UUID)
  • Mention that namespace for OTel metrics changed: https://github.com/maykinmedia/objects-api/pull/737/changes#r2932221728
  • otel_service_name changed -> can we do this without breaking dashboards?
  • changes to setupconfig for objecttypes -> service and use_fields and fields removed (should we remove the step altogether?)
• Check the impact of this release on the Helm charts and make issues for this in https://github.com/maykinmedia/charts if needed, e.g. Align Open Object chart with Open Object version 4.0.0 charts#380
  • New environment variables were added
  • New setup configuration steps or changes to format
  • New containers required
  • ...

To test

• From which version to 4.0 upgrade is upgrade check enforced?
• Test deployment