Internal packages dont report age on PRs #39265
Replies: 3 comments 7 replies
-
|
Which datasource do the packages belong to? |
Beta Was this translation helpful? Give feedback.
-
|
This applies to both maven and npm packages. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsRead the Renovate docs, troubleshooting, self-hosted to learn how to find the logs. Formatting your logsSelect me to read instructionsPlease put your logs in a If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
I'd be happy to provide logs, but I don't know whats relevant to this issue. |
Beta Was this translation helpful? Give feedback.
-
|
If you can share a Job ID, I can see if there are relevant logs to add |
Beta Was this translation helpful? Give feedback.
-
|
019a764b-cc38-7421-8037-9b89bbc0e115 |
Beta Was this translation helpful? Give feedback.
-
|
That being said, I believe this:
is referring to the Merge Confidence functionality, which is only available for public packages. We (Mend) are putting things in place to be able to provide Merge Confidence as an opt-in for Enterprise organisations' internal packages The Merge Confidence badges are separate to the age checks that Renovate will perform for packages for i.e. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I think it is related to Merge Confidence, If its not available for internal packages, then I think it shouldn't be on the PRs at all, displaying Age as Unknown is misleading to users. Yeah, the age checks in Renovate seems to be working correctly. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the feedback - I appreciate your point, at this time, we're not going to make a change to how this is rendered. We wouldn't want to modify the behaviour here as this could lead to someone trying to enumerate known private packages that Mend are aware of Given the badges are (and are intended to be) public and unauthenticated i.e. Additionally, an We could possibly add some functionality to allow hiding anything with |
Beta Was this translation helpful? Give feedback.
-
|
Okay, thank you. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
"renovateVersion": "41.173.1"
Please tell us more about your question or problem
On Renovate PRs packages published to GitHub Packages from internal repositories show Age as Unknown (and Confidence as Neutral), despite metadata about age being present in the logs. Would be helpful to get the actual age of the packages displayed in the PR, like it is for public dependencies.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions