Update dependency @prezly/eslint-config to v5.4.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@prezly/eslint-config	5.2.0 → 5.4.5

---

Release Notes

prezly/code-style (@​prezly/eslint-config)

v5.4.5

Compare Source

v5.4.4

Compare Source

v5.4.3

Compare Source

v5.4.2

Compare Source

v5.4.0

Compare Source

v5.3.2

Compare Source

v5.3.1

Compare Source

v5.3.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 8pm every weekday,every weekend,before 8am every weekday" (UTC), Automerge - "after 8pm and before 8am every weekday,every weekend" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
theme-nextjs-lena-preview	❌ Failed (Inspect)			Jul 10, 2025 11:12pm

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
theme-nextjs-lena-cookbook	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 11:12pm
theme-nextjs-lena-photography	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 11:12pm
theme-nextjs-lena-the-good-newsroom	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 11:12pm

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"15.11.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@"^16.2.0" from @prezly/[email protected]
npm ERR! node_modules/@prezly/eslint-config
npm ERR!   dev @prezly/eslint-config@"5.4.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-05-07T22_12_44_155Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-07T22_12_44_155Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"15.11.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@"^16.2.0" from @prezly/[email protected]
npm ERR! node_modules/@prezly/eslint-config
npm ERR!   dev @prezly/eslint-config@"5.4.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /runner/cache/others/npm/_logs/2026-01-08T22_05_22_533Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-08T22_05_22_533Z-debug-0.log