You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to add opentelemetry-python to the list of well known monorepos in renovate (a prominent automatic dependency update tool you might have heard of) to help grouping related upgrades, I noticed that their datasource for pypi leverages well known Package URLs from metadata to group packages being released from the same monorepo (here is a link to how they parse packages metadata). On the other hand I see that packages being released from opentelemetry-python repository all have a different homepage package url, pointing to their source subfolder within the repo.
Describe the solution you'd like
I'm suggesting to add to all released packages pyproject.tomls an extra package_url label, namely Repository, with value being the opentelemetry-python repo root url (https://github.com/open-telemetry/opentelemetry-python). This will appear close to the Homepage link on Pypi package pages and will be returned by the Pypi JSON api as part of the package's metadata. That would help renovate (once support for the opentelemetry-python monorepo will be added) to suggest upgrading all relevant packages in a single PR, with no need for custom rules to have them grouped.
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
While trying to add opentelemetry-python to the list of well known monorepos in renovate (a prominent automatic dependency update tool you might have heard of) to help grouping related upgrades, I noticed that their datasource for pypi leverages well known Package URLs from metadata to group packages being released from the same monorepo (here is a link to how they parse packages metadata). On the other hand I see that packages being released from opentelemetry-python repository all have a different homepage package url, pointing to their source subfolder within the repo.
Describe the solution you'd like
I'm suggesting to add to all released packages
pyproject.toml
s an extrapackage_url
label, namelyRepository
, with value being the opentelemetry-python repo root url (https://github.com/open-telemetry/opentelemetry-python). This will appear close to theHomepage
link on Pypi package pages and will be returned by the Pypi JSON api as part of the package's metadata. That would help renovate (once support for the opentelemetry-python monorepo will be added) to suggest upgrading all relevant packages in a single PR, with no need for custom rules to have them grouped.Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: