Lock file maintenance

[titouanmathis]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Renovate Bot.

[titouanmathis]

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @studiometa/webpack-config-preset-markdown@6.3.4
npm error Found: remark@15.0.1
npm error node_modules/remark
npm error   remark@"^15.0.1" from @studiometa/webpack-config-preset-markdown@6.3.4
npm error   packages/preset-markdown
npm error     @studiometa/webpack-config-preset-markdown@6.3.4
npm error     node_modules/@studiometa/webpack-config-preset-markdown
npm error       workspace packages/preset-markdown from the root project
npm error       1 more (@studiometa/webpack-config-preset-prototyping)
npm error
npm error Could not resolve dependency:
npm error peer remark@"^14.0.0" from remark-loader@6.0.0
npm error node_modules/remark-loader
npm error   remark-loader@"^6.0.0" from @studiometa/webpack-config-preset-markdown@6.3.4
npm error   packages/preset-markdown
npm error     @studiometa/webpack-config-preset-markdown@6.3.4
npm error     node_modules/@studiometa/webpack-config-preset-markdown
npm error       workspace packages/preset-markdown from the root project
npm error       1 more (@studiometa/webpack-config-preset-prototyping)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-05-07T10_58_16_095Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-05-07T10_58_16_095Z-debug-0.log

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (455ca0e) to head (4cf34c9).
Report is 287 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##             develop      #164   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
+ Complexity        22        21    -1     
===========================================
  Files              5         5           
  Lines             80        89    +9     
===========================================
+ Hits              80        89    +9     

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.