Bump @types/node from 22.10.1 to 22.10.2 #283
Annotations
5 warnings and 2 notices
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Run /./:
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
|
|
Run /./:
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
|
|
Run /./:
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
|
|
Run /./:
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
|
|
Run /./:
dist/index.js#L235
Flagged in freckle/grep-action
|
|
Run /./:
src/grep.ts#L85
Flagged in freckle/grep-action
|
Loading