chore: test #3218
kiriyaga-txfusionci.yml
on: push
Matrix: deploy
Matrix: e2e
Matrix: examples
Matrix: node
Matrix: upgradable
Matrix: verify-vyper
Matrix: verify
Matrix: zksolc
Matrix: zksync-ethers
Matrix: zkvyper
Annotations
82 errors and 17 warnings
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
verify (18, ubuntu)
No overload matches this call.
|
|
verify (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
verify (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
verify (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
verify-vyper (18, ubuntu)
No overload matches this call.
|
|
verify-vyper (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
verify-vyper (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
verify-vyper (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
upgradable (18, ubuntu)
No overload matches this call.
|
|
upgradable (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
upgradable (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
upgradable (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
node (18, macos)
No overload matches this call.
|
|
node (18, macos)
'outputs' is of type 'unknown'.
|
|
node (18, macos)
Parameter 'output' implicitly has an 'any' type.
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
node (18, macos)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
zksync-ethers (18, ubuntu)
No overload matches this call.
|
|
zksync-ethers (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
zksync-ethers (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
zksync-ethers (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
deploy (18, ubuntu)
No overload matches this call.
|
|
deploy (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
deploy (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
deploy (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
node (18, ubuntu)
The job was canceled because "_18_macos" failed.
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
node (18, ubuntu)
No overload matches this call.
|
|
node (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
node (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
node (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './compile/downloader.js'?
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './errors.js'?
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './config-update.js'?
|
|
examples (18, ubuntu)
No overload matches this call.
|
|
examples (18, ubuntu)
'outputs' is of type 'unknown'.
|
|
examples (18, ubuntu)
Parameter 'output' implicitly has an 'any' type.
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
|
|
examples (18, ubuntu)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../errors.js'?
|
|
Run E2E tests on ubuntu
Process completed with exit code 1.
|
|
verify (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
verify-vyper (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
upgradable (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.8.16, 18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
node (18, macos)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksync-ethers (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
deploy (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.4.22, 18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
examples (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zkvyper (18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.8.16, 18, macos)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.4.22, 18, macos)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.7.6, 18, ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.7.6, 18, macos)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.8.16, 18, windows)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
Run E2E tests on ubuntu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|
|
zksolc (0.7.6, 18, windows)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
|