chore(deps): update dependency plotly.js-dist-min to v3.5.1

[renovate-bot-cbcoutinho]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
plotly.js-dist-min	3.5.0 → 3.5.1

---

Release Notes

plotly/plotly.js (plotly.js-dist-min)

v3.5.1

Compare Source

Changed

• Reduce NPM bundle size by removing unneeded files [#​7746]

Fixed

• Fix bug where certain axis.minallowed values could cause axis to be reversed [#​7761]

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate.

[claude]

Claude finished @renovate-bot-cbcoutinho[bot]'s task in 1m 0s —— View job

---

PR Review: plotly.js-dist-min 3.5.0 → 3.5.1

• Gather context
• Review changes
• Post review feedback

---

Summary

This is a clean, low-risk patch dependency update. Only package-lock.json is modified, as expected for a lockfile-only Renovate PR.

Changes in package-lock.json

The diff updates three fields for node_modules/plotly.js-dist-min:

Field	Before	After
version	3.5.0	3.5.1
resolved	…plotly.js-dist-min-3.5.0.tgz	…plotly.js-dist-min-3.5.1.tgz
integrity	sha512-rN+0P4M...	sha512-N2R4RX...

This is exactly the expected change for a patch-level NPM dependency update — version, registry URL, and SHA-512 integrity hash all updated consistently.

Release notes assessment

v3.5.1 ships two changes:

1. Bundle size reduction — unneeded files removed from the NPM package. This is a net positive: smaller install footprint, no API changes.
2. Bug fix: axis.minallowed could reverse axis — I checked the codebase and minallowed is not used in src/App.vue or elsewhere, so this fix does not directly impact this project. It is, however, a harmless improvement.

No concerns

• No package.json changes (version constraints unchanged).
• No source code changes.
• SonarQube quality gate passed with 0 new issues, 0 security hotspots.
• Patch update within the existing ^3.x semver range — fully backwards-compatible.

Verdict

Looks good to merge. This is a routine, safe update with a small upside (reduced bundle size) and no breaking changes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud