Skip to content

Update all dependencies #250

Update all dependencies

Update all dependencies #250

Triggered via pull request October 31, 2023 02:34
Status Failure
Total duration 1m 35s
Artifacts

build-and-test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
test
The message 1 is invalid: * The line 4 of the message (line 2 of the body) exceeds the limit of 72 characters. The line contains 97 characters: "- Replaces deprecated eslint rules with their replacements (some were combined into a single one)". Please reformat the body so that all the lines fit 72 characters. * The line 5 of the message (line 3 of the body) exceeds the limit of 72 characters. The line contains 134 characters: "- Handle non-`Error` error values (existing possible bug, now enforced by TS since catch variables are now `unknown` instead of `any`)". Please reformat the body so that all the lines fit 72 characters. The original message was: Update all dependencies - Updates all the dependencies - Replaces deprecated eslint rules with their replacements (some were combined into a single one) - Handle non-`Error` error values (existing possible bug, now enforced by TS since catch variables are now `unknown` instead of `any`)
test-allow-one-liners
The message 1 is invalid: * The line 4 of the message (line 2 of the body) exceeds the limit of 72 characters. The line contains 97 characters: "- Replaces deprecated eslint rules with their replacements (some were combined into a single one)". Please reformat the body so that all the lines fit 72 characters. * The line 5 of the message (line 3 of the body) exceeds the limit of 72 characters. The line contains 134 characters: "- Handle non-`Error` error values (existing possible bug, now enforced by TS since catch variables are now `unknown` instead of `any`)". Please reformat the body so that all the lines fit 72 characters. The original message was: Update all dependencies - Updates all the dependencies - Replaces deprecated eslint rules with their replacements (some were combined into a single one) - Handle non-`Error` error values (existing possible bug, now enforced by TS since catch variables are now `unknown` instead of `any`)
build
The message 1 is invalid: * The subject must start with a capitalized word, but the current first word is: "change". Please capitalize to: "Change". The original message was: change SomeClass to OtherClass SomeClass with OtherClass
build
The message 1 is invalid: * The subject must start with a capitalized word, but the current first word is: "change". Please capitalize to: "Change". The original message was: change SomeClass to OtherClass Do something The message 2 is invalid: * The first word of the subject ("Change") must not match the first word of the body. Please make the body more informative by adding more information instead of repeating the subject. For example, start by explaining the problem that this change is intended to solve or what was previously missing (e.g., "Previously, ...."). The original message was: Change other subject Change body
test
The following actions uses node12 which is deprecated and will be forced to run on node16: ./. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test-allow-one-liners
The following actions uses node12 which is deprecated and will be forced to run on node16: ./. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/