PIG208 db1edeeabf Fix a broken test case after the Django 4.1 update. (#1093) ...

This fixes the CI starting occur on #1086 and following PRs due to the release
of Django 4.1 (https://docs.djangoproject.com/en/4.1/releases/4.1/) which
shipped the change

    # Even if this relation is not to pk, we require still pk value.
    # The wish is that the instance has been already saved to DB,
    # although having a pk value isn't a guarantee of that.
    if self.instance.pk is None:
        raise ValueError(
            f"{instance.__class__.__name__!r} instance needs to have a primary "
            f"key value before this relationship can be used."
        )

in https://github.com/django/django/pull/15318.

2022-08-09 00:18:08 +03:00

..

test_base.yml

Upgrade mypy support to 0.960 (#973)

2022-05-26 01:20:44 +03:00

test_generic_foreign_key.yml

fix tests for mypy 0.900 (#641)

2021-06-12 01:05:46 +03:00

test_nullable.yml

Bump mypy 0.950 (#939)

2022-04-29 14:44:33 +03:00

test_postgres_fields.yml

Bump mypy 0.950 (#939)

2022-04-29 14:44:33 +03:00

test_related.yml

Fix a broken test case after the Django 4.1 update. (#1093)

2022-08-09 00:18:08 +03:00