[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.6.4 → v0.6.8
• github.com/abravalheri/validate-pyproject: v0.19 → v0.20.2

[jefftriplett]

@joshuadavidthomas we should either drop 3.8 support or add an exclude for your fancy bash script so that Django 5.1 isn't tested with 3.8 or 3.9

[joshuadavidthomas]

@joshuadavidthomas we should either drop 3.8 support or add an exclude for your fancy bash script so that Django 5.1 isn't tested with 3.8 or 3.9

@jefftriplett IIRC, the main part of that happens in this function in the noxfile.py:

django-simple-nav/noxfile.py

Lines 37 to 48 in f043992

	def should_skip(python: str, django: str) -> bool:
	"""Return True if the test should be skipped"""
	if django == DJMAIN and version(python) < version(DJMAIN_MIN_PY):
	# Django main requires Python 3.10+
	return True
	if django == DJ50 and version(python) < version(PY310):
	# Django 5.0 requires Python 3.10+
	return True
	return False

That generates the matrix which the GHA takes and runs with. So just need to add an exception for 5.1

As far as dropping support, I'm not sure. From a high-level, "I am building a public package for others to use" perspective I like trying to support all the versions of Django that are currently supported (so 4.1, 5.0, and 5.1 at the moment) -- unless I am relying specifically on a feature from a new version.

And with that I like trying to hew close to what Django supports for each version, which does include 3.8 and 3.9 for Django 4.1. Though truthfully, I haven't used 3.8 or 3.9 in who know's how long so maybe that's a fool's errand.

Looking at pypistats.org, there are basically no 3.8 downloads and only a handful of 3.9, at least for the past 30 days.

[jefftriplett]

That generates the matrix which the GHA takes and runs with. So just need to add an exception for 5.1

All good. I fiddled around with nox locally and I missed the 50 call. I might have gotten distracted by using nox[uv] which I'll push post your update.