Drop support for python3.7 and bring support for django3.12

[ticosax]

Also test against django releases 4.2 & 5.0
And change dependency to django-fsm-2 a maintained fork of django-fsm.

[ticosax]

@pfouque are you okay with this change ?

[pfouque]

@pfouque are you okay with this change ?

Definitely!

NB: The repository will probably be transferred to django-commons at some point, but it will be transferred with access to the PyPI project!

[pfouque]

LGTM! Thanks!

[ticosax]

merging is blocked by this requirement. But I don't know how to disable it.
Any advice ?

[lorenzomorandini]

@ticosax do you have access to the settings of the repo? I don't but this could be it https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule#deleting-a-branch-protection-rule

[pfouque]

You could try pushing an empty commit to force a new run of those checks ... It may work :)

[ticosax]

@ticosax do you have access to the settings of the repo? I don't but this could be it https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule#deleting-a-branch-protection-rule

unfortunately I don't have access to the settings. @MRigal maybe yourself ?

[ticosax]

You could try pushing an empty commit to force a new run of those checks ... It may work :)

I rebased the branch and it's still the same. Apparently like @lorenzomorandini suggested, it is a branch protection rule.
We will have to call for help with one of the roadies I guess?

[jezdez]

This is now finally unblocked, also see my comment in jazzband/help#368