Skip to content

Implement Config Consistency #11828

Implement Config Consistency

Implement Config Consistency #11828

Triggered via pull request October 7, 2024 20:14
Status Failure
Total duration 46s
Artifacts 1

lambda.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
ubuntu
error SyntaxError: /home/runner/work/dd-trace-js/dd-trace-js/package.json: Unexpected token < in JSON at position 1679 at JSON.parse (<anonymous>) at /usr/local/lib/node_modules/yarn/lib/cli.js:1629:59 at Generator.next (<anonymous>) at step (/usr/local/lib/node_modules/yarn/lib/cli.js:310:30) at /usr/local/lib/node_modules/yarn/lib/cli.js:321:13
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "supported-integrations". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
ubuntu
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ubuntu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/checkout@v2, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
supported-integrations Expired
0 Bytes