Skip to content

Allow custom registry support for -version datasources #45023

Description

@jamietanna

We have a number of language/tool version Datasources like photon-version that don't have customRegistrySupport = true, but we do have support in golang-version, gradle-version, and node-version.

We should make sure that all -version Datasources do have a custom registry supported, so we can allow self-hosted users to override their settings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority-3-mediumDefault priority, "should be done" but isn't prioritised ahead of others

    Type

    Fields

    Priority

    None yet

    Datasource

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions