Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings emitted during GitHub Workflow execution #2828

Closed
cweider opened this issue Jun 21, 2023 · 1 comment · Fixed by #2830, #2831, #2846 or #2848
Closed

Warnings emitted during GitHub Workflow execution #2828

cweider opened this issue Jun 21, 2023 · 1 comment · Fixed by #2830, #2831, #2846 or #2848

Comments

@cweider
Copy link
Collaborator

cweider commented Jun 21, 2023

There are many warnings from the actions run in the checks of pull_request. Virtually all relate to deprecation of one kind or another.

The majority of issues relate to:

Both of which are of the variety “we’re turning this off in Summer 2023” – which would be bad. Enforcement of Node16 became effective on the 14th of June (with no serious effects) and collective inaction has led the set-state command disabling to be postponed indefinitely (from 31st of May 2023). Nevertheless, the deprecated command should be replaced – it’s best to address these warnings on a schedule we control.

@cweider
Copy link
Collaborator Author

cweider commented Jun 21, 2023

Tally of workflow warnings:

 3 Automate build and deploy
 3 CodeQL
 8 Lint
 0 Push new dev images
 1 Semgrep
50 docker build and test
 0 Sentry-release

@cweider cweider changed the title Warnings emitted during GitHub Workflow execution. Warnings emitted during GitHub Workflow execution Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment