Closed dependabot[bot] closed 1 year ago
@Mergifyio refresh
refresh
/test centos-ci/sink-clustered/mini-k8s-1.26
/test centos-ci/sink-clustered/mini-k8s-1.26
I had to trigger the run manually as the author is outside approved contributor's list.
Automatic merge is pending due to #285.
Looks like mergify is waiting for check-success=centos-ci/sink-clustered/mini-k8s-1.25
to be run successfully. @anoopcs9 is this a valid rule still? Do we need to run this OR do we have yet another out of date thing in the mergify config?
Next time I'll read your entire comment. :-D
⚠️ This pull request got rebased on behalf of a random user of the organization. This behavior will change on the 1st February 2023, Mergify will pick the author of the pull request instead.
To get the future behavior now, you can configure bot_account
options (e.g.: bot_account: { author }
or update_bot_account: { author }
.
Or you can create a dedicated github account for squash and rebase operations, and use it in different bot_account
options.
/test centos-ci/sink-clustered/mini-k8s-1.26
Bumps github.com/prometheus/client_golang from 1.11.0 to 1.11.1.
Release notes
Sourced from github.com/prometheus/client_golang's releases.
Changelog
Sourced from github.com/prometheus/client_golang's changelog.
... (truncated)
Commits
989baa3
promhttp: Check validity of method and code label values (#962) (#987)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/samba-in-kubernetes/samba-operator/network/alerts).