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

Robot Upgrade: prometheus-node-exporter chart upgrade from 4.6.0 to 4.42.0 #2673

Closed
wants to merge 1 commit into from

Conversation

weizhoublue
Copy link
Member

I am robot, upgrade: project prometheus-node-exporter chart upgrade from 4.6.0 to 4.42.0

@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch 8 times, most recently from 55c0336 to e087de3 Compare November 13, 2024 20:09
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch 7 times, most recently from e85e1f1 to 7ebfcfb Compare November 20, 2024 20:09
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch 8 times, most recently from 547601a to 898dbc1 Compare November 28, 2024 20:09
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch 4 times, most recently from 68ea7b3 to 0c5968d Compare December 2, 2024 20:09
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch 7 times, most recently from 7000e7c to c1caa23 Compare December 9, 2024 20:10
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch 4 times, most recently from 7c244a2 to 3695e7c Compare December 13, 2024 20:10
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.42.0 branch from 3695e7c to 75c6c85 Compare December 14, 2024 20:10
@weizhoublue
Copy link
Member Author

robot: found newer version 4.43.0

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.

2 participants