Skip to content

Bump @types/node from 22.10.5 to 22.10.6 #292

Bump @types/node from 22.10.5 to 22.10.6

Bump @types/node from 22.10.5 to 22.10.6 #292

Triggered via pull request January 14, 2025 00:48
Status Success
Total duration 11s
Artifacts

example.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 warnings and 2 notices
grep
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Use of setFailed is considered harmful: src/main.ts#L92
Imagine if setFailed was a dangerous function. This annotation will highlight its usage in diffs. And this body would describe why that is, what nuances or trade-offs, the author should consider, and perhaps some options to use instead. This bit doesn't support markdown, sadly, but maybe someday? https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
Use of setFailed is considered harmful: src/main.ts#L95
Imagine if setFailed was a dangerous function. This annotation will highlight its usage in diffs. And this body would describe why that is, what nuances or trade-offs, the author should consider, and perhaps some options to use instead. This bit doesn't support markdown, sadly, but maybe someday? https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
Use of setFailed is considered harmful: src/main.ts#L98
Imagine if setFailed was a dangerous function. This annotation will highlight its usage in diffs. And this body would describe why that is, what nuances or trade-offs, the author should consider, and perhaps some options to use instead. This bit doesn't support markdown, sadly, but maybe someday? https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
Use of setFailed is considered harmful: src/reporter.ts#L83
Imagine if setFailed was a dangerous function. This annotation will highlight its usage in diffs. And this body would describe why that is, what nuances or trade-offs, the author should consider, and perhaps some options to use instead. This bit doesn't support markdown, sadly, but maybe someday? https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
Minimal configuration test: dist/index.js#L235
Flagged in freckle/grep-action
Minimal configuration test: src/grep.ts#L85
Flagged in freckle/grep-action