New release triggers migrations

[hansegucker]

The current release is missing a migration:

Migrations for 'recurrence':
  .tox/lint/lib/python3.13/site-packages/recurrence/migrations/0003_alter_date_id_alter_param_id_alter_recurrence_id_and_more.py
    ~ Alter field id on date
    ~ Alter field id on param
    ~ Alter field id on recurrence
    ~ Alter field id on rule

[hartungstenio]

django-recurrence should define a default_auto_field in it's AppConfig.

Django 6.0 changed the DEFAULT_AUTO_FIELD setting default value to BigAutoField. This migration probably has something to do with this change.

[AndreyObviously]

Any news?

[Natureshadow]

Normally, the type of auto field should be a project-wide setting. Django has warned about this since 3.2. The issue only occurs for projects that never cared to set DEFAULT_AUTO_FIELD despite this warning.

[vogelier]

Our company has also just run into this issue. @lino, stemming from https://docs.djangoproject.com/en/6.0/releases/6.0/#default-auto-field-setting-now-defaults-to-bigautofield and just wondering if, based on the guidance in the release notes, it'd just be as simple as adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to the settings.py and then running the makemigrations command.

I'm happy to contribute that unless you foresee any knock-on issues. Would be great to get this into a release soon as it means anyone using Django 6.x simply can't use this library.

[AndreyObviously]

django-recurrence should define a default_auto_field in it's AppConfig.

from django.apps import AppConfig


class RecurrenceConfig(AppConfig):
    default_auto_field = "django.db.models.BigAutoField"
    name = "recurrence"