Skip to content

ci: trigger compatibility workflow on the feature branch #1

ci: trigger compatibility workflow on the feature branch

ci: trigger compatibility workflow on the feature branch #1

Triggered via push May 31, 2026 22:17
Status Failure
Total duration 32m 0s
Artifacts 1
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 1 warning
compatibility
Failed test were found and 'fail-on-error' option is set to true
compatibility
go tool mockgen -package=mock_client -source=client.go -destination=mock/client/client.go (generated, 1166ms)
compatibility
go tool mockgen -package=mock_rpcclient -source=client.go -destination=mock/client/client.go (generated, 483ms)
compatibility
go tool go-bindata -modtime=1700000000 -pkg migrations -o ../bindata.go ./ (generated, 85ms)
compatibility
go tool mockgen -package=mock_settings -source=database_settings_manager.go -destination=mock/database_settings_manager.go (generated, 402ms)
compatibility
go tool go-bindata -modtime=1700000000 -pkg migrations -o ../bindata.go ./ (generated, 66ms)
compatibility
go tool go-bindata -modtime=1700000000 -pkg migrationsprevnodecfg -o ../bindata.go ./ (generated, 79ms)
compatibility
go tool go-bindata -modtime=1700000000 -pkg migrations -o ../bindata.go ./ (generated, 296ms)
compatibility
go tool mockgen -source=contracts.go -destination=mock/contracts.go (generated, 339ms)
compatibility
go tool mockgen -package=mock_persistence -source=interface_persistence.go -destination=./mock/persistence.go (generated, 1335ms)
compatibility
go run main.go (generated, noplugin, 175ms)
compatibility
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, actions/setup-python@v4, actions/upload-artifact@v4, dorny/test-reporter@95058abb17504553158e70e2c058fe1fda4392c2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
compatibility-logs
1.55 MB
sha256:0798a9529a0ffe46e060b15451acb3377daa302996253a43113b6f46177380e1