Skip to content

chore(logme): Switch to new SDK structure #4143

chore(logme): Switch to new SDK structure

chore(logme): Switch to new SDK structure #4143

Triggered via pull request April 2, 2026 07:45
Status Failure
Total duration 1m 39s
Artifacts

ci.yaml

on: pull_request
Code coverage report
Code coverage report
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
CI
Process completed with exit code 2.
CI: stackit/internal/services/logme/instance/resource.go#L745
G115: integer overflow conversion int -> int32 (gosec)
CI: stackit/internal/services/logme/instance/resource.go#L743
G115: integer overflow conversion int64 -> int32 (gosec)
CI: stackit/internal/services/logme/instance/resource.go#L945
rangeValCopy: each iteration copies 144 bytes (consider pointers or indexing) (gocritic)
CI: stackit/internal/services/logme/instance/resource.go#L912
rangeValCopy: each iteration copies 144 bytes (consider pointers or indexing) (gocritic)
CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. 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/