[VietND96]

Summary

Fixes #3274.

Since the 4.49.0 release, update_tag_in_docs_and_files.sh's whole-tree sed has matched nothing in 51 files (charts/selenium-grid/values.yaml, the docker-compose-*.yml files, the kubernetes/*.yaml manifests, docs/docker-hub/*.md, README.md, NodeDocker/config.toml, NodeKubernetes/config.toml, ...):

• The old sort-based LATEST_TAG resolution (git tag --sort=-version:refname) picked 4.48.0-20261010 (lexically highest) instead of the real previous tag 4.48.0-20260905, so the release's sed "s/${LATEST_TAG}/${NEXT_TAG}/g" found no match and these files were never rewritten for the 4.49.0 release.
• [ci] Fix LATEST_TAG sort picking a stale tag and skipping the chart bump #3254 fixed the resolution method going forward (switched to ancestry-based git describe --tags --abbrev=0, per the comment now in deploy.yml), but it only manually caught up Chart.yaml/CONFIGURATION.md, not these 51 files.
• Every release since then searches for the immediately-preceding tag, which is never what's actually still embedded in these files (frozen several releases back), so they can't self-heal without a one-time manual catch-up - exactly the trap this repo's own CLAUDE.md documents: "anything version-shaped that is not the exact previous tag is invisible to it and will go stale silently."

Confirmed on trunk before this fix: charts/selenium-grid/values.yaml's imageTag/nodesImageTag/videoImageTag were still 4.48.0-20260905/ffmpeg-8.1-20260905 while Chart.yaml's appVersion was already 4.51.0-20261010 - so a default chart install runs Grid 4.48.0 images under chart 0.62.0, as the issue describes.

What this does

Ran ./update_tag_in_docs_and_files.sh 4.48.0-20260905 4.51.0-20261010 locally (the real previous tag, not what resolution would currently find) and reviewed the resulting diff by hand. It touched 55 files; I reverted 4 that shouldn't be in scope:

• .github/workflows/deploy.yml: the stale tag there appears only inside a comment narrating this exact past incident by its specific values (the comment explaining why git describe replaced the sort-based resolution). Rewriting it would corrupt the history it's documenting.
• charts/selenium-grid/multiple-nodes-platform-version.yaml and tests/charts/ci/multiple-nodes-platform-version-values.yaml: these pin per-Chrome-version image tags (146.0-20260905, 145.0-20260905, ...), each dated independently of the Grid release cadence via the separate browser-version release process. The script's date-only sed pass matched their 20260905 by coincidence, not because they're stale in the same way as the Grid tag - a real fix for these needs its own, separate pass.
• tests/ci/test_cleanup_pr_images.py: synthetic example tag strings in a regex-matching unit test (test_rejects_release_and_floating_tags), unrelated to live defaults.

The Makefile's own comment (an illustrative example of the exact-tag format, not a historical narration) picked up the date-only correction and is now self-consistent again, so I kept that one.

Test plan

• Confirmed no 4.48.0-20260905 / ffmpeg-8.1-20260905 occurrences remain outside CHANGELOG.md and the 4 deliberately-excluded files.
• Verified every restored tag is a real, currently published image: selenium/hub:4.51.0-20261010, selenium/standalone-{firefox,chrome,chromium,edge}:4.51.0-20261010, selenium/video:ffmpeg-8.1-20261010 all return 200 from the Docker Hub API, and the GitHub release 4.51.0-20261010 linked from README.md exists.
• Ran make lint_format_scripts (regenerates charts/selenium-grid/CONFIGURATION.md via helm-docs) - no further diff beyond the 51 files, confirming values.yaml and CONFIGURATION.md are already consistent.
• Validated YAML parses correctly on a sample of the touched files (values.yaml, a K8s manifest, a docker-compose file).

🤖 Generated with Claude Code

[qodo-code-review]

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing