Skip to content

move code from src/ to v.mod subdirs #860

move code from src/ to v.mod subdirs

move code from src/ to v.mod subdirs #860

Triggered via push April 22, 2026 10:45
Status Failure
Total duration 2m 15s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

13 errors, 7 warnings, and 6 notices
macos-clang
Process completed with exit code 1.
macos-clang
cannot use `string` as `int` in argument 2 to `App.admin_users`
macos-clang
cannot use `string` as `int` in argument 2 to `App.admin_users`
macos-clang
cannot use `string` as `int` in argument 2 to `App.admin_users`
ubuntu-gcc
Process completed with exit code 1.
ubuntu-gcc
cannot use `string` as `int` in argument 2 to `App.admin_users`
ubuntu-gcc
cannot use `string` as `int` in argument 2 to `App.admin_users`
ubuntu-gcc
cannot use `string` as `int` in argument 2 to `App.admin_users`
windows-gcc
Process completed with exit code 1.
ubuntu-tcc
Process completed with exit code 1.
ubuntu-tcc
cannot use `string` as `int` in argument 2 to `App.admin_users`
ubuntu-tcc
cannot use `string` as `int` in argument 2 to `App.admin_users`
ubuntu-tcc
cannot use `string` as `int` in argument 2 to `App.admin_users`
macos-clang
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
macos-clang
casting `&C.git_object` to `&C.git_commit` is only allowed in `unsafe` code
ubuntu-gcc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
ubuntu-gcc
casting `&C.git_object` to `&C.git_commit` is only allowed in `unsafe` code
windows-gcc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
ubuntu-tcc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
ubuntu-tcc
casting `&C.git_object` to `&C.git_commit` is only allowed in `unsafe` code
macos-clang
unused parameter: `text`
macos-clang
unused parameter: `repository_name`
ubuntu-gcc
unused parameter: `text`
ubuntu-gcc
unused parameter: `repository_name`
ubuntu-tcc
unused parameter: `text`
ubuntu-tcc
unused parameter: `repository_name`