Skip to content

[bugfix] Ensure consistent behaviour when using access token from session in GQL and REST clients #13587

[bugfix] Ensure consistent behaviour when using access token from session in GQL and REST clients

[bugfix] Ensure consistent behaviour when using access token from session in GQL and REST clients #13587

Triggered via pull request November 21, 2024 23:35
Status Failure
Total duration 1m 11s
Artifacts

ci.yml

on: pull_request
Matrix: CI
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
CI_Node_22
@shopify/shopify-api#build: command (/home/runner/work/shopify-app-js/shopify-app-js/packages/apps/shopify-api) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (2)
CI_Node_22
Process completed with exit code 2.
CI_Node_20
The job was canceled because "_22" failed.
CI_Node_20
@shopify/shopify-api#build: command (/home/runner/work/shopify-app-js/shopify-app-js/packages/apps/shopify-api) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (2)
CI_Node_20
The operation was canceled.
CI_Node_18
The job was canceled because "_22" failed.
CI_Node_18
@shopify/shopify-api#build: command (/home/runner/work/shopify-app-js/shopify-app-js/packages/apps/shopify-api) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (2)
CI_Node_18
The operation was canceled.
CI_Node_22
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/