Skip to content

feat(ingress): support wildcard custom domains #142

feat(ingress): support wildcard custom domains

feat(ingress): support wildcard custom domains #142

Triggered via pull request March 16, 2026 14:53
Status Success
Total duration 25s
Artifacts

validate-examples.yml

on: pull_request
check-all
20s
check-all
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
check-all: custom-domain/dstack-ingress/docker-compose.multi.yaml#L39
39:15 [empty-values] empty value in block mapping
check-all: custom-domain/dstack-ingress/CLOUDFORMATION_EXAMPLE.yaml#L6
6:13 [trailing-spaces] trailing spaces
check-all: custom-domain/dstack-ingress/CLOUDFORMATION_EXAMPLE.yaml#L6
6:13 [empty-values] empty value in block mapping
check-all: custom-domain/dstack-ingress/docker-compose.yaml#L24
24:13 [empty-values] empty value in block mapping
check-all: tor-hidden-service/docker-compose.yml#L38
38:12 [empty-values] empty value in block mapping
check-all: tor-hidden-service/docker-compose.yml#L35
35:7 [empty-values] empty value in block mapping
check-all
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/