Ülgen Sarıkavak

@alexgmin > but from my memory, the reason we're not using 3.13 is that Trac doesn't work on that version since it used some of the standard library removals, and...

> Sounds like Trac could use some attention as well then to keep it up-to-date with the latest Python - is there a tracking issue for that? The last time...

> Since Trac has the history of the Django project we can think to contribute to it to let it survive, at least the Python version upgrade. I mostly agree...

About > It's more important that they run the same Django version (because they share a database, and technically Django doesn't support running two different versions talking to the same...

> ...I guess one potential issue would be: https://github.com/django/djangoproject.com/pull/2105 django-hosts update is handled in https://github.com/django/djangoproject.com/pull/2253

@bmispelon Thank you 🌻 I can help with 3.14 update too but is there any concerns about Python - Django - Trac version compability between this repo and code.djangoproject.com? I...

@bmispelon Hey again and sorry for the ping, would you mind giving your approval if everything is okay on preview server?

A nice reading about Renovate's position in its area: https://www.jvt.me/posts/2024/04/12/use-renovate/

@jacobtylerwalls Thanks for taking the time to discuss this, but I'm sorry that the main concern here is just a misunderstanding. * Renovate doesn't need org-level umbrella permissions that gives...

> For context, N+1 issues are created on the server, the SDK just provides the spans. Thanks for the info. > This sounds like a usecase for archiving/deleting/ignoring issues in...