Skip to content

HashEscrow: separate hash-based escrow identity flow (#1657) #6736

HashEscrow: separate hash-based escrow identity flow (#1657)

HashEscrow: separate hash-based escrow identity flow (#1657) #6736

Triggered via pull request June 12, 2026 16:24
Status Failure
Total duration 2m 27s
Artifacts

golangci-lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
lint
issues found
lint: token/services/interop/hashescrow/transaction.go#L77
cannot use map[any]any{} (value of type map[any]any) as map[string]any value in assignment (typecheck)
lint: token/services/interop/hashescrow/transaction.go#L65
cannot use map[any]any{} (value of type map[any]any) as map[string]any value in assignment
lint: token/services/interop/hashescrow/transaction.go#L53
cannot use map[any]any{} (value of type map[any]any) as map[string]any value in assignment
lint: token/services/interop/hashescrow/transaction.go#L41
cannot use map[any]any{} (value of type map[any]any) as map[string]any value in assignment
lint
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, golangci/golangci-lint-action@v8. 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/