Drop support for Django 3.0.

[hramezani]

No description provided.

[codecov]

Codecov Report

Merging #1461 (e0b1332) into main (8b280e1) will increase coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1461      +/-   ##
==========================================
+ Coverage   86.50%   86.60%   +0.10%     
==========================================
  Files          34       34              
  Lines        1852     1852              
  Branches      260      260              
==========================================
+ Hits         1602     1604       +2     
+ Misses        178      177       -1     
+ Partials       72       71       -1     

Impacted Files	Coverage Δ
debug_toolbar/panels/signals.py	86.36% <0.00%> (+4.54%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b280e1...e0b1332. Read the comment docs.

[matthiask]

Thanks! Do you have any idea where the coverage decrease comes from? We cannot drop backwards compatibility shims yet because of 2.2, I'm a bit surprised that it changed anything...

[hramezani]

Thanks! Do you have any idea where the coverage decrease comes from?

I don't know exactly. based on the report it comes from debug_toolbar/panels/profiling.py lines 64,66,68 which seems weird to me.
After I pushed another commit it passed successfully 🤷‍♂️

[hramezani]

We cannot drop backwards compatibility shims yet because of 2.2, I'm a bit surprised that it changed anything...

The 3.0.x series no longer receive security updates or bug fixes.

[matthiask]

The 3.0.x series no longer receive security updates or bug fixes.

Yes, but since we still support the older 2.2 series we cannot drop any backwards compatibility code yet.

Still, let's merge this since faster CI runs are good (tm).