increase supported range for Next.js to version 16.0 #41991
node-test.yml
on: push
Matrix: unit
Matrix: agent_evals_build
Matrix: check-json-schema
Matrix: check-package-lock-vsce
Matrix: check-package-lock
Matrix: lint
Matrix: vscode_unit
Matrix: integration-windows
Matrix: integration
Annotations
37 errors and 21 warnings
|
integration (20, npm run test:storage-emulator-integration)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:storage-emulator-integration)
The operation was canceled.
|
|
integration-windows (20, npm run test:client-integration)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:client-integration)
The operation was canceled.
|
|
integration-windows (20, npm run test:frameworks)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:frameworks)
The operation was canceled.
|
|
integration-windows (20, npm run test:emulator)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:emulator)
The operation was canceled.
|
|
integration (20, npm run test:hosting)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:hosting)
The operation was canceled.
|
|
integration-windows (20, npm run test:triggers-end-to-end:inspect)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The operation was canceled.
|
|
integration (20, npm run test:functions-discover)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:functions-discover)
The operation was canceled.
|
|
integration (20, npm run test:extensions-emulator)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:extensions-emulator)
The operation was canceled.
|
|
integration (20, npm run test:client-integration)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:client-integration)
The operation was canceled.
|
|
integration (20, npm run test:import-export)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:import-export)
The operation was canceled.
|
|
integration (20, npm run test:triggers-end-to-end:inspect)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:triggers-end-to-end:inspect)
The operation was canceled.
|
|
integration (20, npm run test:frameworks)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:frameworks)
The operation was canceled.
|
|
integration (20, npm run test:triggers-end-to-end)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:triggers-end-to-end)
The operation was canceled.
|
|
integration-windows (20, npm run test:storage-deploy)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:storage-deploy)
The operation was canceled.
|
|
integration (20, npm run test:emulator)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration (20, npm run test:emulator)
The operation was canceled.
|
|
integration-windows (20, npm run test:hosting)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:hosting)
The operation was canceled.
|
|
integration-windows (20, npm run test:functions-discover)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:functions-discover)
The operation was canceled.
|
|
vscode_unit (20)
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
vscode_unit (20)
The operation was canceled.
|
|
CI Tests
Canceling since a higher priority waiting request for CI Tests-push-leoortizz_nextjs16 exists
|
|
integration-windows (20, npm run test:client-integration)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:client-integration)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:client-integration)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:frameworks)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:frameworks)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:frameworks)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:emulator)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:emulator)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:emulator)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:storage-deploy)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:storage-deploy)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:storage-deploy)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:hosting)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:hosting)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:hosting)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:functions-discover)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:functions-discover)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration-windows (20, npm run test:functions-discover)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|