New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ignore "empty" Go module updates #5123
Comments
Do you have any ideas for how Renovate could "know" that? e.g. would an option "skip the PR completely if there's no change to |
If the update only changes the files |
Is the only way to determine this is after |
Since I don’t know renovate’s codebase, I don’t think I can answer the question |
It's a Go question, not a Renovate question. If a Go dependency is not using modules (uses commits instead) and the commit is updated, can you tell if it's an "empty" change without running |
Man, I’m sorry but I’m doing this on my free time. I have no idea how deep into the guts you need to go to not run the whole “go mod vendor” stuff. There’s clearly a world in which you can dig into that code to do less work but I have no idea what it entails |
Hi there, Help us by making a minimal reproduction repository. Before we can start work on your issue we first need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. To get started, please read our guide on creating a minimal reproduction to understand what is needed. We may close the issue if you (or someone else) have not provided a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment. Good luck, The Renovate team |
Hello there, Is there a way to gracefully abort and then ignore the upgrade with a PostUpgradeTask? That would allow us to detect and solve the above issue in a self-hosted deployment. |
Possibly a script which:
Although manipulating Essential that someone can create a reproduction |
See here: https://github.com/thejan2009/renovate-go-5123
Edit: we want github.com/stretchr/testify@v1.8.0 to be upgraded only if there are changes |
I got a little further by modifying your And I confirmed manually that the comment correctly reset the values. The problem is that today we match fileFilters against the output of |
Confirmed I could get the anticipated result with a bit of code mod:
But I need to think if there's a cleaner way |
Blocked by #18609 |
So, I'm getting lots of PRs like jmhodges/lekube#94, where the only changes are to the commit hash in the 3 files managed by the Go module system. There's no actual code changes in there beyond the version bump, because the Go module system (correctly) sees there were no relevant updates to the subpackages used by lekube.
It'd be cool if these "empty" PRs didn't happen. I get them every few days because those repos have new commits often. It's making pay less attention to all of my renovate PRs, because these "empty" PRs are far more common than the useful PRs.
The text was updated successfully, but these errors were encountered: