-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Regression in helm v3 manager does not bump the version of the chart #17681
Comments
Hi there, Get your issue 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. To get started, please read our guide on creating a minimal reproduction. We may close the issue if you, or someone else, haven't created 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 |
Hi there, We have found that there's a problem with the logs. 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 appClick me to read instructionsIf you use the Renovate app (GitHub):
Finding logs when self-hostingClick me to read instructionsIf you're running self-hosted, run with Insufficient logsClick me to read instructionsIf you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section. Formatting your logsClick me to read instructionsPlease put your logs in a
|
Hello there~ I am not able to create a more valid reproduction environment than the one I have just passed where there are two PRs created in a different moment that one works and the other one do not. The same dependency is used in other charts that are also failling:
But it is working on this one: Logs from Mend Renovate Dashboardnewrelic/helm-charts: #803510665
newrelic/nri-kubernetes: #803544881
The only difference I can see is that in the one that is not working it jumps directly from
To:
without even testing
I cannot give you logs from the same repository because the successful run was 9 days ago and I have logs up to 4 days ago, sorry. |
When a bug has been marked as needing a reproduction, it means nobody can work on it until one is provided. In cases where no reproduction is possible, or the issue creator does not have the time to reproduce, we unfortunately need to close such issues as they are non-actionable and serve no benefit by remaining open. This issue will be closed after 7 days of inactivity. |
This bug report has been closed as we need a reproduction to work on this. If the original poster or anybody else with the same problem discovers that they can reproduce it, please create a new issue, and reference this issue. |
I was able to reproduce it again but only that day. That day GitHub also had an incident regarding Actions: https://www.githubstatus.com/incidents/sqcs1d0yk16q We also had a broken pipeline that, to be able to fix it, we had to close and reopen the PR with the same commits from another branch. So I think that the pipeline simply glitched. I am sorry for the possible noise I could have made. |
How are you running Renovate?
Mend Renovate hosted app on github.com
Was this something which used to work for you, and then stopped?
It used to work, and then stopped
Describe the bug
It is known that renovate is unable to bump the version of the chart when it is updating
helm-values
: #8231But until yesterday, the chart version was raised without any issue while updating dependencies to other charts in the
Chart.yaml
file but the last attempts are not bumping it.Have you created a minimal reproduction repository?
No reproduction, but I have linked to a public repo where it occurs
The text was updated successfully, but these errors were encountered: