Skip to content
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

chore(deps): update dependency newrelic/nri-prometheus to v2.21.3 #1879

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 12, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
newrelic/nri-prometheus patch v2.21.2 -> v2.21.3

Release Notes

newrelic/nri-prometheus (newrelic/nri-prometheus)

v2.21.3

Compare Source

⛓️ Dependencies

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner June 12, 2024 16:19
Copy link
Contributor Author

renovate bot commented Jun 12, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

@renovate renovate bot force-pushed the renovate/newrelic-nri-prometheus-2.x branch 5 times, most recently from 585da21 to 2d48303 Compare June 17, 2024 06:05
@renovate renovate bot force-pushed the renovate/newrelic-nri-prometheus-2.x branch from 2d48303 to 1d04f47 Compare June 17, 2024 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants