Skip to content

refactor: migrate example configs from vercel.json to vercel.ts #580

refactor: migrate example configs from vercel.json to vercel.ts

refactor: migrate example configs from vercel.json to vercel.ts #580

Triggered via pull request March 26, 2026 02:48
@amondnetamondnet
synchronize #300
Status Failure
Total duration 28s
Artifacts

deploy.yml

on: pull_request_target
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
deploy
The process 'npx' failed with exit code 1
deploy
Original attempt errors: npm warn exec The following package was not found and will be installed: vercel@41.1.4 npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me npm warn deprecated path-match@1.2.4: This package is archived and no longer maintained. For support, visit https://github.com/expressjs/express/discussions npm warn deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated tar@4.4.18: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me Vercel CLI 41.1.4 Error: You cannot set your Personal Account as the scope.
deploy
Original attempt output:
deploy
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
deploy
Vercel CLI rejected the org ID as a personal account scope. Retrying without VERCEL_ORG_ID (VERCEL_PROJECT_ID is still set).