feat: sanitize release names upon submission
Description
- Clean release name field to ensure no errors when loading release pages
Closes #2724
@JacobCoffee is there an issue associated with this PR? I mean it makes sense but hard to say if it is "correct" without some documenting reason.
yeah sorry, i thought if i put it in the commit message it would link it
doh...
before i do all the migrations and things, do you think overriding the name on the NameSlugModel and adding the validator is still the best path @ewdurbin? I'm okay with either just wanting to make sure
This should also allows pre-release names such as:
- Python 3.15.0a1, Python 3.15.0b2, Python 3.15.0rc3
And we now also have Python install manager releases with names like:
- Python install manager 25.0
- Python install manager 25.1 beta 1
https://www.python.org/admin/downloads/release/
Also this PR has flipped the order of Slug and Name:
Let's keep Name first like in production: