Skip to content
CI

Use new getApiKeyAndHeaders to fetch the API key from the model registry #167

Sign in to view logs

Use new getApiKeyAndHeaders to fetch the API key from the model registry

Use new getApiKeyAndHeaders to fetch the API key from the model registry #167

Re-run triggered May 2, 2026 09:57
@mgabor3141mgabor3141
#41
kirberich:fix-getApiKey
Status Failure
Total duration 1m 16s
Artifacts –

ci.yml

on: pull_request
check
1m 12s
check
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
check
Process completed with exit code 1.
check
Argument of type 'import("/home/runner/work/yapp/yapp/packages/safeguard/node_modules/@mariozechner/pi-coding-agent/dist/core/extensions/types").ExtensionContext' is not assignable to parameter of type 'import("/home/runner/work/yapp/yapp/packages/budget-model/node_modules/@mariozechner/pi-coding-agent/dist/core/extensions/types").ExtensionContext'.
check
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/setup-node@v4. 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/