Skip to content

CCM-17047: Add client , campaign and supplier name to Grafana dashboard #365

CCM-17047: Add client , campaign and supplier name to Grafana dashboard

CCM-17047: Add client , campaign and supplier name to Grafana dashboard #365

Triggered via pull request May 13, 2026 11:03
Status Success
Total duration 5m 46s
Artifacts

pr_closed.yaml

on: pull_request
check-merge-or-workflow-dispatch
2s
check-merge-or-workflow-dispatch
Deploy changes to main in dev AWS account  /  Validate deployment request
4s
Deploy changes to main in dev AWS account / Validate deployment request
Check for event schemas package version change
9s
Check for event schemas package version change
Deploy changes to main in dev AWS account  /  Deploy backend
5m 24s
Deploy changes to main in dev AWS account / Deploy backend
Test contracts (provider)
Test contracts (provider)
Deploy changes to main in dev AWS account  /  Deploy proxy
Deploy changes to main in dev AWS account / Deploy proxy
Publish event schemas package to GitHub package registry
0s
Publish event schemas package to GitHub package registry
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Check for event schemas package version change
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/