chore(deployment): switch workflow telemetry action#6369
Conversation
|
Claude finished @corneliusroemer's task in 48s —— View job Code Review
This is a minimal, well-justified change. A few notes: Security Switching from Maintainability The workflow file has no inline comment explaining why a fork is used. Future maintainers will see an unusual fork reference with a raw SHA and wonder why. A short comment like Overall: Change looks good. Switching from an unmaintained action with old Node runtime to a pinned fork is the right call. Confirm the fork's provenance and optionally add a comment before merging. |
There was a problem hiding this comment.
Pull request overview
Switches the integration-test workflow telemetry step from the unmaintained Catchpoint action to the maintained ycfreeman fork, while pinning to a specific commit for reproducibility/supply-chain safety.
Changes:
- Replaced
catchpoint/workflow-telemetry-action@v2withycfreeman/workflow-telemetry-action@cad169ff11f718319d5468b0a67a238db000ef3fin the integration tests workflow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
anna-parker
left a comment
There was a problem hiding this comment.
like not blocking but this fork doesnt seem to be too used, just dont want us to switch to sth and have issues in the future: https://github.com/ycfreeman/workflow-telemetry-action
That's how forks start, someone takes over maintenance
Not a problem, we can just disable/reevaluate then. It's not a big deal, but the action is helpful see for example #6370 where I use it to see what CPU load is. |
|
@anna-parker @theosanderson would be good to either replace (this PR) or remove the action (in another PR if you prefer) as it's just producing a lot of noise right now:
|

Summary
This PR switches the integration test workflow telemetry step from unmaintained and broken
catchpoint/workflow-telemetry-action@v2to the maintained forkycfreeman/workflow-telemetry-action, pinned to commitcad169ff11f718319d5468b0a67a238db000ef3f.The upstream Catchpoint action currently only publishes
v2/v2.0.0, which still uses the older Node runtime.This action has been useful to see CPU/disk usage and timing of integration test workflow.
Testing
New action works and produces good results
Graphs look like this:
🚀 Preview: Add
previewlabel to enable