Repository navigation
Feedback wanted: Getting started + "week 1" problems #41411
Replies: 8 comments 4 replies
|
Submission:This is definitely a week 1 problem: #28164 (summary: #28164 (reply in thread)) |
|
Hi Renovate maintainers,
Main onboarding pain point in a self-hosted GitHub App + Permissions that had to be added (and how each was discovered):
Not granted:
Caching changes needed for stability/performance:
NPM registry host tuning that was unexpectedly required:
Failure signaling was confusing:
Suggestion:
|
|
For me, I had two things that were pretty surprising to me when I started with renovate:
EDIT: Almost forgot:
|
|
Still in my first week of self-hosting (working together with a self-hosted Forgejo).
|
|
First: I absolutely love the idea of having a chapter called "Getting started", when I first came to Renovate and was overwhelmed by the documentation. |
|
We have a lot of difficulties using renovate with a private docker registry to update our own image references. If there is an example how to configure the credentials correctly, we didn't find it. Also most AI models hallucinate a lot of renovate config which either does not exist or is deprecated. Maybe a cookbook of common configurations could help improve the user experience and the AI support. |
|
An issue that prevents us from using it in some of our projects is that tool installations do not respect |
|
I was aware of this forum post before I started working on using Renovate, so along the way of my journey I made notes of things that I found confusing. This post is the combination of my notes into something readable by someone else. The incomplete draft of this post has been sitting untouched in my Emacs buffer for a couple of weeks so I feel this post is a fair representation of "the first week" even if the calendar time is almost a month by the time of making this post. Since there are some bullets with questions, I'll answer those first: Onboarding for self-hosting is a bit rough. I started from the Renovate configuration in the astral-sh organization since they tend to know what they are doing, and I'm sure that made things a lot easier. My main source of information is searching with DuckDuckGo, and I don't use AI. SummaryAfter reading a lot of documentation and various third-party blog posts to try to figure out how to set up a self-hosted Renovate on GitHub, it was this blog post that put all the pieces together for me: https://blog.ostebaronen.dk/2025/10/self-hosted-renovate-github.html. I'm not sure if the documentation is designed to "nudge" people away from self-hosting, but it feels like the documentation containing a checklist with the required 5/7/10 steps to set up a self-hosted Renovate would have been enough to eliminate a lot of my confusion. Once I had the self-hosted Renovate on GitHub up and running, the experience has been generally pleasant. There are definitely some puzzling parts, but the overall impression is solid. Here are the top 5 of my list in no particular order:
I'm guessing the average Renovate user is technically skilled, so it must increase your support burden that it's so difficult to test things locally. I just want to know what Renovate is going to update and to which version, so a log level between info and debug (info+?) would be sufficient for 95% of my needs so far. I can't imagine why a dependency without version constraints would be interpreted as "not a candidate for security updates" for Someone just curious about the big picture can stop reading at this point, but since I kept notes along the way I've put the rest of my findings not yet mentioned under the headings below. Suspected bugsrenovate/config-validation fails with "No config file found"Renovate runs just fine after the change is merged, so I'm not sure why the renovate/config-validation job can't find the config file, or how to fix the problem. Example PR: DigitalEarthSweden/.github#9 Pull request didn't trigger renovate/config-validationExample PR: DigitalEarthSweden/.github#11 No pull request for GDAL 3.13.3 despite being detected in dashboardExpanding the detected Dockerfile dependencies in the dashboard (DigitalEarthSweden/digital-earth-sweden-community#114) shows GDAL 3.13.2. Renovate doesn't seem to detect that GDAL 3.13.3 has been released for some reason though. Debug logs of Renovate if that helps: https://github.com/DigitalEarthSweden/.github/actions/runs/32563175390/job/97007811973 Pull request didn't contain the updateThis later went in as an automatic lockfile update on Monday morning, but this pull request is missing the part of the package update somehow: DigitalEarthSweden/digital-earth-sweden-community#124 Pull request Pull request is in unstable statusHere's a log excerpt I saved, I assume the double "Pull request Pull request" in the message is some kind of bug. Surprising behaviors/help wantedLock-file update pull request don't contain description of what is updatedLooking at the Renovate logs, uv prints information about what it updates, and this information is captured by Renovate and echoed into the logs. Would be terrific to get this information into the pull request Renovate makes as well. I'm only asking for the information Renovate has already captured to be relayed, I'm not asking for additional information beyond that. Local testingIf I could wish freely, I would have a local mode that creates the branches with the changes but doesn't push them to the remote repository/make pull requests out of them, but I'm sure you've already thought about that so there's some technical reason it's not implemented. Here are the other things I've noticed while trying to test things locally. Disallowing Node 26 from being usedI installed the Renovate CLI through npm and discovered that it doesn't let me use the Node 26 that is available in the path. I'm sure there are valid reasons for this, but from a user perspective it feels quite restrictive to have to downgrade my Node installation to run the Renovate CLI. Optimistic strict config validationDuring the initial trial and error to get things running, I discovered that some settings had to be in If everything is accepted even in the strict mode is because of usability concerns, I would be happy with a
|
Uh oh!
There was an error while loading. Please reload this page.
We (the Renovate maintainers) are looking to understand the point-of-view for early users of Renovate.
(if you have some feedback from the first few weeks of using Renovate, that's also welcome!)
For instance:
config:js-apporconfig:js-lib?Feel free to share anything that's relevant, including the above questions, or anything else.
We're looking for free-form responses.
All reactions