Skip to content

[Snyk] Upgrade moment from 2.29.4 to 2.30.1 #8

[Snyk] Upgrade moment from 2.29.4 to 2.30.1

[Snyk] Upgrade moment from 2.29.4 to 2.30.1 #8

Triggered via pull request August 16, 2024 20:05
Status Failure
Total duration 6m 16s
Artifacts

linting.yml

on: pull_request
detect changed files
8s
detect changed files
Copied files are in sync
8s
Copied files are in sync
Changelogger use
19s
Changelogger use
Changelogger validity
1m 0s
Changelogger validity
Project structure
39s
Project structure
PHP Code Sniffer (non-excluded files only)
0s
PHP Code Sniffer (non-excluded files only)
PHP Compatibility
0s
PHP Compatibility
PHP Code Sniffer (changes to excluded files only)
0s
PHP Code Sniffer (changes to excluded files only)
ESLint (non-excluded files only)
0s
ESLint (non-excluded files only)
ESLint (changes to excluded files only)
0s
ESLint (changes to excluded files only)
Lint GitHub Actions yaml files
0s
Lint GitHub Actions yaml files
Check linter exclude lists
0s
Check linter exclude lists
Lock files are up to date
1m 57s
Lock files are up to date
Monorepo package version refs
22s
Monorepo package version refs
Matrix: php_lint
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Changelogger use
Project github-actions/repo-gardening is being changed, but no change file in projects/github-actions/repo-gardening/changelog/ is touched! Use `jetpack changelogger add github-actions/repo-gardening` to add a change file. Guidelines: https://github.com/Automattic/jetpack/blob/trunk/docs/writing-a-good-changelog-entry.md
Changelogger use
Process completed with exit code 2.
Project structure
Process completed with exit code 1.
Monorepo package version refs
Process completed with exit code 1.
Lock files are up to date: pnpm-lock.yaml#L1
pnpm-lock.yaml is not up to date! You can probably fix this by running `pnpm install` in the appropriate directory.
Lock files are up to date
Process completed with exit code 1.