Add found Version to dashboard

[wuast94]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

gitea running rennovate 39.7.1-full in a docker container

Please tell us more about your question or problem

At the moment it seems not possible to see if renovate is detecting every dep successfull. i have a huge list of regex versioning and so on and the only possible way to see if renovate is detecting everything right and WOULD make the right update is to downgrade the dep and see if a PR gets created. The logs also only show the update if an update exists.

If i didnt missed anything (and i googled alot and searched diskussions etc) it would be nice if there would be some sort of list with current and latest detected package or something like that, maybee in the dashboard where renovate lists all found deps it coud add the latest found version matching the set rules after this.

this way we could easy and fast check if all is right. if the versions match its fine, if there is an update the new version is listed and also everything ok, if there is no latest version something is wrong.

renovate detects all my deps but if its all working i dont know, the only way as i said i know at the moment is to downgrade all versions, and see if renovate picks them all up. in the picture for example, if i would have the worng versioning it would show up exactly like that but would never make an update becouse a wrong versioning would never find the right new version.

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

Minimal repo
https://github.com/wuast94/renovatetest

[rarkins]

Renovate already lists the full list of detected dependencies, it also lists updates (both open and pending). It also has a warning if any lookups have failed. What edge case are you worried about missing?

[wuast94]

but my test repo shows exactly the problem that renovate dont show anything to me that would show me that my config dont work.

so basicly what you say is that i have to downgrade all my packages (hundreds) and manually check if renovate creates a pull request for all of them. that is the only way at the moment to check if my config is working with my packages and their versioning.

[wuast94]

look at the sonarr package, there is a newer version availalble, but my allowedVersion is wrong and thats the reason renovate dont find a matching newer version, the only problem is that renovate dont show this anywhere. so a simple log output what is the parsed version found remote would solve all problems

[wuast94]

Sorry, but I don't like this idea and won't be accepting it as a feature request. You already get warnings if lookups fail (satisfying the NULL case) and the extra "noise" to satisfy occasional edge cases like you worry about is not worth it to the majority of users

also which warnings? i dont get any warnings that renovate didnt find any tag that matches my regex nor any info about it:

{
            "autoReplaceStringTemplate": "{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}",
            "currentDigest": "sha256:98c21a64377619ec74778c70cc2e74d3e978a4d2c61f97b9ad88a0e5bc0766f9",
            "currentValue": "4.0.9.2244-ls255",
            "currentVersion": "4.0.9.2244-ls255",
            "currentVersionAgeInDays": 49,
            "currentVersionTimestamp": "2024-09-20T23:37:13.723Z",
            "datasource": "docker",
            "depName": "linuxserver/sonarr",
            "fixedVersion": "4.0.9.2244-ls255",
            "homepage": "https://github.com/linuxserver/docker-sonarr/packages",
            "lookupName": "linuxserver/sonarr",
            "packageName": "linuxserver/sonarr",
            "registryUrl": "https://index.docker.io",
            "replaceString": "linuxserver/sonarr:4.0.9.2244-ls255@sha256:98c21a64377619ec74778c70cc2e74d3e978a4d2c61f97b9ad88a0e5bc0766f9",
            "sourceUrl": "https://github.com/linuxserver/docker-sonarr",
            "versioning": "regex:^(?<prerelease>develop-)?v?(?<major>\\d+)\\.?(?<minor>\\d+)?\\.?(?<patch>\\d+)?(?:ubu\\d+)?(?:\\.|-)?(?<build_old>\\w?\\d+)?-ls(?<build>\\d+)$",
            "warnings": [],
            "updates": []
          },

it dont even show me my allowedVersion regex in there. if i look at this i would say everything is fine but it isnt.

renovate does that matching anyways, would it that dealbreaking to just add one line that says foundVersion: whith the version extracted and matched against our rules?

[rarkins]

It's a no. For most users, showing "disallowed" versions (those not satisfying allowedVersions) in the dashboard would be highly undesirable

[Motobyter]

I have found this issue, because I am seeking a similar solution.

Currently, when I modify a custom regex for versioning, I can't see what Renovate is capturing during a run, especially if an image has been previously tagged. As I need to add and optimize the regex for many instances, it is essential to check the results in the debug log to determine if it is correctly detecting the current target version.

The problem arises when my regex fails; in that case, Renovate may not inform me because it has already found a version and will not update the instance to a future version. This undermines Renovate’s primary functionality.

Additionally, if the instance provider changes its version naming convention, I wouldn’t be able to notice this issue either.

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team