[denanmusinovic]

Problem

The Release Charts workflow on main is failing at cr package:

Error: can't get a valid version for repositories simple-service. Try changing the version constraint in Chart.yaml

Root cause

The org-rename commit (NeuraLegion -> BrightSec) made text edits inside several charts, which marked them as "changed" so chart-releaser now tries to package them. These charts pinned simple-service to old versions (0.0.1 / 0.3.0 / 0.4.0) with no vendored subchart tgz and no Chart.lock. The local simple-service is now 0.5.0, so the pin can't be resolved and packaging fails. This was a latent issue; the rename just woke it up by touching the charts.

Fix

For the 7 affected (changed + broken) charts: bump the simple-service dependency pin to 0.5.0, vendor simple-service-0.5.0.tgz, generate Chart.lock, and bump each chart version.

chart	chart version	simple-service pin
ao-reauth-triggers	0.0.2 -> 0.0.3	0.3.0 -> 0.5.0
ao-sms-otp	0.0.2 -> 0.0.3	0.4.0 -> 0.5.0
auto-resolve	0.0.2 -> 0.0.3	0.3.0 -> 0.5.0
benchmarking-webdriver-target	0.0.3 -> 0.0.4	0.0.1 -> 0.5.0
dynamic-link-server	0.0.4 -> 0.0.5	0.0.1 -> 0.5.0
rate-limit-server	0.0.2 -> 0.0.3	0.3.0 -> 0.5.0
stresstesting-webdriver	0.0.3 -> 0.0.4	0.0.1 -> 0.5.0

Verification

• helm dependency update succeeds for all 7 (tgz + Chart.lock generated)
• helm lint passes for all 7
• helm package succeeds for all 7 (the exact step that failed in CI)

Notes / follow-up

• This bumps the subchart from old versions to 0.5.0, which may change rendered output for these testground apps. Acceptable for vulnerable-apps, but flagging the behavior change.
• Other charts still have the same latent issue (missing vendored tgz) but were not touched by the rename, so they are not packaged yet and will break if edited later: chaotic-shop, commix, juice-shop, labbank, log4shell, loadbenchmark, ssti-suite-*, static-site, vulhub-appweb, vulhub-tomcat, vulnlab, xvwa. Worth a separate cleanup pass.