Skip to content

fix: Truncate cname to a max of 63 chars #4574

fix: Truncate cname to a max of 63 chars

fix: Truncate cname to a max of 63 chars #4574

Triggered via pull request September 6, 2024 20:27
Status Success
Total duration 26m 28s
Artifacts

build.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Verify code
Unexpected input(s) 'skip-pkg-cache', 'skip-build-cache', valid inputs are ['version', 'install-mode', 'working-directory', 'github-token', 'only-new-issues', 'skip-cache', 'skip-save-cache', 'problem-matchers', 'args', 'cache-invalidation-interval']
Verify code
Unexpected input(s) 'skip-pkg-cache', 'skip-build-cache', valid inputs are ['version', 'install-mode', 'working-directory', 'github-token', 'only-new-issues', 'skip-cache', 'skip-save-cache', 'problem-matchers', 'args', 'cache-invalidation-interval']
Run integration tests
The following actions uses node12 which is deprecated and will be forced to run on node16: engineerd/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run integration tests
The following actions use a deprecated Node.js version and will be forced to run on node20: engineerd/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/