Norbert Szulc

Should https://github.com/renovatebot/renovate/pull/27733/commits/7babd040765c76e4c362991193197cb652f86e51 be moved to separate PR? Maybe `normalizePythonDepName` should be moved to a different module, as it is now widely used?

This may break configs where they match for `some_package` or `some.package`.

Can we get a resolution on that PR? I'm getting a lot of conflicts on force-pushes to `v38` and less will to resolve them every time.

[My objections](https://github.com/renovatebot/renovate/pull/27733#pullrequestreview-2018268937) to changes related to [this change request](https://github.com/renovatebot/renovate/pull/27733#discussion_r1574967662) are still unresolved. I'm pointing this out as they are now hidden in this thread.

re: request hungry This is data source is cached. And I see 3 requests if Python version is detected: * python.org for all versions * endoflife.date for EOL status *...

I found that Python versioning is not returning `newValue`. I have implemented proper function by reusing `poetry.getNewValue`. It worked, and it created a PR. Here is a working config. ```json...

Is there anything blocking release of this data source?

I think it would be best to reflect this in the project's description then. Maybe create a highlighted text pointing out the migration.

We discussed this with @PyroX2 and we came to conclusion that we need to drop support for gazebo-11 in this image.

Documentation is a bit lackluster about this. https://goauthentik.io/docs/property-mappings/ What was not obvious was the need to navigate to **Customisation > Property Mappings**. There I could set something up.  Then...