We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/kind bug
What steps did you take and what happened: Pipeline Schedule - Update Bot is not working for customize, see e.g. https://github.com/SovereignCloudStack/cluster-stack-provider-openstack/actions/runs/9317239967/job/25647136793 - "Failed to look up github-tags package kubernetes-sigs/kustomize extractVersion=^kustomize\\/v(?<version>.+)$"
Schedule - Update Bot
"Failed to look up github-tags package kubernetes-sigs/kustomize extractVersion=^kustomize\\/v(?<version>.+)$"
What did you expect to happen: Kustomize renovated to kustomize/v5.4.2
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
/etc/os-release
The text was updated successfully, but these errors were encountered:
I had a look at how other are handling regex and I found the following patch.
https://github.com/toolhippie/kubectl/pull/113/files
I think we can simply rely on using github-tags here.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
/kind bug
What steps did you take and what happened:
Pipeline
Schedule - Update Bot
is not working for customize, see e.g. https://github.com/SovereignCloudStack/cluster-stack-provider-openstack/actions/runs/9317239967/job/25647136793 -"Failed to look up github-tags package kubernetes-sigs/kustomize extractVersion=^kustomize\\/v(?<version>.+)$"
What did you expect to happen:
Kustomize renovated to kustomize/v5.4.2
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
)/etc/os-release
):The text was updated successfully, but these errors were encountered: