feat(identity-mapper): allow machineuids #11268
JamesDoingStuffci.yaml
on: push
graph_proxy_code
/
lint
1m 17s
graph_proxy_code
/
test
2m 5s
auth_daemon_code
/
lint
1m 33s
auth_daemon_code
/
test
31s
github_pages
/
lint_docs
10s
github_pages
/
build_docs
20s
github_pages
/
build_storybook
1m 16s
detect_files_changed
4s
sessionspaces_code
/
lint
1m 26s
sessionspaces_code
/
test
31s
helm_lint
/
lint
33s
kyverno_policy
/
test-policy
3m 58s
auth_core_code
/
lint
56s
auth_core_code
/
test
1m 7s
commit_lint
/
lint
18s
telemetry_code
/
lint
1m 10s
telemetry_code
/
test
56s
dev_resources
/
build
58s
lint_workflows
13s
release_please
/
release-please
graph_proxy_container
/
build
20s
auth_daemon_container
/
build
6m 47s
github_pages
/
publish_pages
identity_mapper_code
/
python
identity_mapper_container
/
build
oidc_bff_container
/
build
6m 38s
sessionspaces_container
/
build
5m 52s
dashboard_container
/
build_container
3m 50s
Annotations
12 warnings
|
detect_files_changed
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
helm_lint / lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
github_pages / lint_docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: borales/actions-yarn@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
kyverno_policy / test-policy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
graph_proxy_container / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.18.0, docker/metadata-action@v5.10.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
supergraph_update
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/create-github-app-token@v1.11.0, actions/download-artifact@v4.1.8, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
frontend_code / lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
oidc_bff_container / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.18.0, docker/metadata-action@v5.9.0, docker/setup-buildx-action@v3.11.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
sessionspaces_container / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.18.0, docker/metadata-action@v5.10.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
frontend_code / test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
auth_daemon_container / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.18.0, docker/metadata-action@v5.10.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
dashboard_container / build_container
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6.0.0, docker/build-push-action@v6.18.0, docker/metadata-action@v5.10.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
DiamondLightSource~workflows~DPTOBT.dockerbuild
|
60 KB |
sha256:25489a8d920c326659a2aacad997f5e6d4a7c50f6ebaec224abfca5ed025e5dc
|
|
|
DiamondLightSource~workflows~JMO4XJ.dockerbuild
|
86.4 KB |
sha256:7f1be6dea99ba201763ba49a71b132b435c55e88b5b943379e94388a487cedeb
|
|
|
DiamondLightSource~workflows~M6L3UE.dockerbuild
|
87.5 KB |
sha256:f2ce0be4a146f5b5fbfdb57aad9b1fa23520e07904a0b3e4603a8c7d155141c4
|
|
|
DiamondLightSource~workflows~SH2JCP.dockerbuild
|
72.5 KB |
sha256:5029c6c5d0fad6373d9b3991eedbbc7dc9fdc607147e399e1402aa23b47b00c6
|
|
|
DiamondLightSource~workflows~UCFBTM.dockerbuild
|
53.9 KB |
sha256:f76f87f048ea762a49056b562e0aafa6f3ad6b385652065de6fd63b8465fd7cc
|
|
|
coverage.html
|
61.4 KB |
sha256:c5f827ce9a596d50638a3b15aada435c6c4d77050eeb23cad172d0d08c63a660
|
|
|
docs
|
1.1 MB |
sha256:39417f31c755132f85dc74ff3990a8aaee68e2793b2619e43d6c24172885d30f
|
|
|
graph-proxy
|
2.82 KB |
sha256:03fd42e53e4375c333f3a30fd9cf4c7a189f5ab98b57f7f69454fceddd3d2a5f
|
|
|
router-execution-config
|
14.7 KB |
sha256:c2ab8f42d8984304e7ae0454d1f9fe48be333b75ba59fed3602763f75e01b615
|
|
|
storybook
|
2.65 MB |
sha256:ff1aeb0dcc542a1d642702f8b0af9347502c6f6bbbdd6bd8a300312ca4751a5b
|
|
|
supergraph-schema
|
5.1 KB |
sha256:0710debdc68e896e7116b107266fcad8f86495b23de45d59e4cda8bed3f102ad
|
|