[gjulivan]

added configuration: Allow values above maximum.

solving : #2464

[github-actions]

AI Code Review

✅ Approved — no issues found

---

What was reviewed

File	Change
progress-circle-web/src/ProgressCircle.xml, typings/ProgressCircleProps.d.ts	New boolean property allowValueAboveMax (default false) and its matching typings
progress-circle-web/src/util.ts	calculatePercentage takes an allowValueAboveMax flag and removes floating-point noise before rounding
progress-circle-web/src/components/ProgressCircle.tsx	The above-max error is suppressed when allowed. A widget-progress-circle-overflow class is added. The ring stays full because the animate call still uses the clamped percentage.
progress-circle-web/src/ProgressCircle.tsx, .editorPreview.tsx, .editorConfig.ts	The flag is passed through to the runtime and the preview. The Studio Pro check is skipped when the flag is on.
progress-circle-web/src/__tests__/util.spec.ts, components/__tests__/ProgressCircle.spec.tsx	New unit tests for the percentage maths and the overflow behaviour
progress-circle-web/CHANGELOG.md	User-facing entry under [Unreleased]

Skipped (out of scope): none

CI: pending: Run code quality check, Plan E2E matrix, sigridci · unrelated failures: security/snyk (external scanner; the code and license Snyk checks pass)

---

Positives

• The change is backward compatible: the new property defaults to false, so existing apps behave as before.
• The edge cases are tested: empty range, max below min, values below min, and rounding.
• The changelog entry describes behavior for app developers and mentions the new CSS class.