Skip to content
CI

pdf-server: CommandQueue, Vercel deployment, improved tool description #1710

Sign in to view logs

pdf-server: CommandQueue, Vercel deployment, improved tool description

pdf-server: CommandQueue, Vercel deployment, improved tool description #1710

Triggered via pull request March 30, 2026 16:02
@ochafikochafik
opened #575
pdf-server-command-queue-vercel
Status Success
Total duration 9m 18s
Artifacts –

ci.yml

on: pull_request
Auto-fix formatting
33s
Auto-fix formatting
e2e
6m 49s
e2e
Build (Windows WSL)
9m 13s
Build (Windows WSL)
Matrix: build
Matrix: test-git-install
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
e2e
No file matched to [/home/runner/work/ext-apps/ext-apps/**/*requirements*.txt,/home/runner/work/ext-apps/ext-apps/**/*requirements*.in,/home/runner/work/ext-apps/ext-apps/**/*constraints*.txt,/home/runner/work/ext-apps/ext-apps/**/*constraints*.in,/home/runner/work/ext-apps/ext-apps/**/pyproject.toml,/home/runner/work/ext-apps/ext-apps/**/uv.lock,/home/runner/work/ext-apps/ext-apps/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Build (Windows WSL)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6. 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/