Skip to content

feat(builds): add the possibility to configure insecure registries #16083

feat(builds): add the possibility to configure insecure registries

feat(builds): add the possibility to configure insecure registries #16083

Triggered via pull request May 7, 2026 09:51
Status Success
Total duration 1m 25s
Artifacts

pull-request-test.yml

on: pull_request
Analyze deploy strings
5s
Analyze deploy strings
changes
5s
changes
Deploy on Azure
50s
Deploy on Azure
Ensure no custom components
2s
Ensure no custom components
Cleanup
0s
Cleanup
Documentation
0s
Documentation
Matrix: Cypress slow acceptance tests
Matrix: Cypress acceptance tests
Fit to window
Zoom out
Zoom in

Annotations

1 warning
changes
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 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/