Skip to content

chore(ci): convert hypatia-scan.yml to wrapper of standards reusable #112

chore(ci): convert hypatia-scan.yml to wrapper of standards reusable

chore(ci): convert hypatia-scan.yml to wrapper of standards reusable #112

Triggered via pull request May 26, 2026 12:17
Status Failure
Total duration 3h 49m 2s
Artifacts

dogfood-gate.yml

on: pull_request
Validate A2ML manifests
2s
Validate A2ML manifests
Validate K9 contracts
7s
Validate K9 contracts
Empty-linter (invisible characters)
31s
Empty-linter (invisible characters)
Groove manifest check
34s
Groove manifest check
Dogfooding compliance summary
5s
Dogfooding compliance summary
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 6 warnings
Validate A2ML manifests
Failed to download archive 'https://codeload.github.com/hyperpolymath/a2ml-validate-action/tar.gz/59145c7d1039fa3059b3ecacdb50ee23d7505898' after 1 attempts.
Validate A2ML manifests
An action could not be found at the URI 'https://codeload.github.com/hyperpolymath/a2ml-validate-action/tar.gz/59145c7d1039fa3059b3ecacdb50ee23d7505898' (24C0:1537DF:1CC7C2:251CC1:6A1594CA)
Validate K9 contracts
Process completed with exit code 1.
Validate K9 contracts
K9 validation failed with 2 error(s)
Validate K9 contracts: ./verisimdb/connectors/test-infra/deploy.k9.ncl#L1
Pedigree block missing 'name' field (in pedigree.metadata.name or pedigree.name)
Validate K9 contracts: ./verisimdb/connectors/test-infra/deploy.k9.ncl#L1
Missing K9! magic number. First non-empty line must be exactly 'K9!'
Empty-linter (invisible characters)
The process '/usr/bin/git' failed with exit code 128
Empty-linter (invisible characters)
unable to access 'https://github.com/hyperpolymath/nextgen-databases/': The requested URL returned error: 403
Empty-linter (invisible characters)
unable to access 'https://github.com/hyperpolymath/nextgen-databases/': The requested URL returned error: 403
Empty-linter (invisible characters)
unable to access 'https://github.com/hyperpolymath/nextgen-databases/': The requested URL returned error: 403
Groove manifest check
expected 'packfile'
Groove manifest check
RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
Groove manifest check
expected 'packfile'
Groove manifest check
RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
Dogfood Gate
Internal server error. Correlation ID: 1da320ce-dda9-495c-a89c-a42ace5fd501
Validate K9 contracts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/
Validate K9 contracts: ./verisimdb/connectors/test-infra/deploy.k9.ncl#L1
No security level (leash/security_level) found in pedigree block
Validate K9 contracts: ./verisimdb/connectors/test-infra/deploy.k9.ncl#L1
Pedigree block missing 'version' or 'schema_version' field
Empty-linter (invisible characters)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/
Groove manifest check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/
Dogfooding compliance summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/