Zap regen command to generate matter files #58
AryaHassanliAnnotations
8 errors and 1 warning
|
build
Process completed with exit code 1.
|
|
build:
cmd/action/zapdiff.go#L42
zapCmd.Run undefined (type *cli.ZAP has no field or method Run)
|
|
build:
cmd/action/zapdiff.go#L41
zapCmd.NoProgress undefined (type *cli.ZAP has no field or method NoProgress)
|
|
build:
cmd/action/zapdiff.go#L40
zapCmd.ConformanceXML undefined (type *cli.ZAP has no field or method ConformanceXML)
|
|
build:
cmd/action/zapdiff.go#L39
zapCmd.FeatureXML undefined (type *cli.ZAP has no field or method FeatureXML)
|
|
build:
cmd/action/zapdiff.go#L38
zapCmd.Attribute undefined (type *cli.ZAP has no field or method Attribute)
|
|
build:
cmd/action/zapdiff.go#L37
zapCmd.SdkRoot undefined (type *cli.ZAP has no field or method SdkRoot)
|
|
build:
cmd/action/zapdiff.go#L36
zapCmd.Root undefined (type *cli.ZAP has no field or method Root)
|
|
build
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 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/
|