feat: migrate zlog to zig 0.15.1 #12
hendriknielaenderAnnotations
1 error and 14 warnings
|
build (windows-latest)
Process completed with exit code 1.
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: DonIsaac/zlint-action@v0, mlugg/setup-zig@v2. 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/
|
|
suppressed-errors:
examples/otel_example.zig#L21
`catch` statement suppresses errors
|
|
unsafe-undefined:
src/async_batcher.zig#L95
Do not use `undefined` as a default value
|
|
unsafe-undefined:
src/async_batcher.zig#L94
Do not use `undefined` as a default value
|
|
unsafe-undefined:
src/async_batcher.zig#L27
Do not use `undefined` as a default value
|
|
unsafe-undefined:
src/async_batcher.zig#L22
Do not use `undefined` as a default value
|
|
suppressed-errors:
src/async_batcher.zig#L185
Caught error is mishandled with `unreachable`
|
|
avoid-as:
src/otel.zig#L195
Prefer using type annotations over @as().
|
|
unsafe-undefined:
src/zlog.zig#L112
Do not use `undefined` as a default value
|
|
unsafe-undefined:
src/zlog.zig#L111
Do not use `undefined` as a default value
|
|
unsafe-undefined:
src/writer_handle.zig#L67
comparing with `undefined` is unspecified behavior.
|
|
build (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@v2. 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/
|
|
build (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@v2. 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/
|
|
build (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@v2. 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/
|