Skip to content

[Snyk] Upgrade @wordpress/i18n from 4.55.0 to 4.58.0 #176

[Snyk] Upgrade @wordpress/i18n from 4.55.0 to 4.58.0

[Snyk] Upgrade @wordpress/i18n from 4.55.0 to 4.58.0 #176

Triggered via pull request June 6, 2024 18:50
Status Failure
Total duration 2m 28s
Artifacts

linting.yml

on: pull_request
detect changed files
9s
detect changed files
Copied files are in sync
6s
Copied files are in sync
Changelogger use
21s
Changelogger use
Changelogger validity
57s
Changelogger validity
Project structure
24s
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 59s
Lock files are up to date
Monorepo package version refs
24s
Monorepo package version refs
Matrix: php_lint
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Changelogger use
Project packages/publicize is being changed, but no change file in projects/packages/publicize/changelog/ is touched! Use `jetpack changelogger add packages/publicize` 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.