reviewdog: Too many results (annotations) in diff. You may miss some annotations due to GitHub limitation for annotation created by logging command. Please check GitHub Actions log console to see all results. Limitation: - 10 warning annotations and 10 error annotations per step - 50 annotations per job (sum of annotations from all the steps) - 50 annotations per run (separate from the job annotations, these annotations aren't created by users) Source: https://github.com/orgs/community/discussions/26680#discussioncomment-3252835

reviewdog: Too many results (annotations) in diff. You may miss some annotations due to GitHub limitation for annotation created by logging command. Please check GitHub Actions log console to see all results. Limitation: - 10 warning annotations and 10 error annotations per step - 50 annotations per job (sum of annotations from all the steps) - 50 annotations per run (separate from the job annotations, these annotations aren't created by users) Source: https://github.com/orgs/community/discussions/26680#discussioncomment-3252835

[misspell] reported by reviewdog 🐶 "optimise" is a misspelling of "optimize" Raw Output: ./js/react_native/e2e/package-lock.json:272:32: "optimise" is a misspelling of "optimize"

[misspell] reported by reviewdog 🐶 "optimise" is a misspelling of "optimize" Raw Output: ./js/react_native/e2e/package-lock.json:162:23: "optimise" is a misspelling of "optimize"

[misspell] reported by reviewdog 🐶 "optimise" is a misspelling of "optimize" Raw Output: ./js/react_native/package-lock.json:319:23: "optimise" is a misspelling of "optimize"

[misspell] reported by reviewdog 🐶 "optimise" is a misspelling of "optimize" Raw Output: ./js/react_native/package-lock.json:270:32: "optimise" is a misspelling of "optimize"

[misspell] reported by reviewdog 🐶 "optimise" is a misspelling of "optimize" Raw Output: ./js/react_native/package-lock.json:153:23: "optimise" is a misspelling of "optimize"

[misspell] reported by reviewdog 🐶 "marshalled" is a misspelling of "marshaled" Raw Output: ./js/react_native/cpp/EpContextDataReadCallback.h:24:7: "marshalled" is a misspelling of "marshaled"

[misspell] reported by reviewdog 🐶 "analogue" is a misspelling of "analog" Raw Output: ./js/web/test/unittests/pool-output-shape.ts:38:67: "analogue" is a misspelling of "analog"

[misspell] reported by reviewdog 🐶 "colour" is a misspelling of "color" Raw Output: ./js/web/test/e2e/exports/testcases/nextjs-default/package-lock.json:917:14: "colour" is a misspelling of "color"

[misspell] reported by reviewdog 🐶 "colour" is a misspelling of "color" Raw Output: ./js/web/test/e2e/exports/testcases/nextjs-default/package-lock.json:26:23: "colour" is a misspelling of "color"

[misspell] reported by reviewdog 🐶 "marshalled" is a misspelling of "marshaled" Raw Output: ./js/node/src/inference_session_wrap.cc:71:43: "marshalled" is a misspelling of "marshaled"

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions-rs/toolchain@16499b5e05bf2e26879000db0c1d13f7e13fa3af. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

[cpplint] reported by reviewdog 🐶 Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5] Raw Output: go/onnxruntime/onnxruntime_c_api.h:1185: Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5]

[cpplint] reported by reviewdog 🐶 Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5] Raw Output: go/onnxruntime/onnxruntime_c_api.h:1081: Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5]

[cpplint] reported by reviewdog 🐶 Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5] Raw Output: go/onnxruntime/onnxruntime_c_api.h:1039: Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5]

[cpplint] reported by reviewdog 🐶 Include the directory when naming header files [build/include_subdir] [4] Raw Output: go/onnxruntime/onnxruntime_c_api.h:37: Include the directory when naming header files [build/include_subdir] [4]

[cpplint] reported by reviewdog 🐶 Include the directory when naming header files [build/include_subdir] [4] Raw Output: go/onnxruntime/cshim.h:4: Include the directory when naming header files [build/include_subdir] [4]

[cpplint] reported by reviewdog 🐶 #endif line should be "#endif // GO_ONNXRUNTIME_CSHIM_H_" [build/header_guard] [5] Raw Output: go/onnxruntime/cshim.h:219: #endif line should be "#endif // GO_ONNXRUNTIME_CSHIM_H_" [build/header_guard] [5]

[cpplint] reported by reviewdog 🐶 #ifndef header guard has wrong style, please use: GO_ONNXRUNTIME_CSHIM_H_ [build/header_guard] [5] Raw Output: go/onnxruntime/cshim.h:1: #ifndef header guard has wrong style, please use: GO_ONNXRUNTIME_CSHIM_H_ [build/header_guard] [5]

[cpplint] reported by reviewdog 🐶 No copyright message found. You should have a line: "Copyright [year] <Copyright Owner>" [legal/copyright] [5] Raw Output: go/onnxruntime/cshim.h:0: No copyright message found. You should have a line: "Copyright [year] <Copyright Owner>" [legal/copyright] [5]

[cpplint] reported by reviewdog 🐶 Include the directory when naming header files [build/include_subdir] [4] Raw Output: go/onnxruntime/cshim.c:1: Include the directory when naming header files [build/include_subdir] [4]

[cpplint] reported by reviewdog 🐶 No copyright message found. You should have a line: "Copyright [year] <Copyright Owner>" [legal/copyright] [5] Raw Output: go/onnxruntime/cshim.c:0: No copyright message found. You should have a line: "Copyright [year] <Copyright Owner>" [legal/copyright] [5]

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"