Thanks for providing the detailed commit instructions. However, I not…

[ghost]

…ice that the diff shows unstaged changes, but you've asked me to generate a commit message based on staged changes.

The diff header shows:

Full Diff of Unstaged Changes (2 selected files)

Important: Commit messages should be generated from staged changes (files added with git add). Unstaged changes are work-in-progress modifications that haven't been marked for commit yet.

If you intended to commit these changes, please:

1. Stage them first: git add README.md values.yaml
2. Then I can generate an appropriate commit message

---

That said, if these changes are what you want to commit, here's the conventional commit message:

docs: add image versioning strategy and Chainguard usage explanation

Add comprehensive documentation explaining why the chart uses Chainguard's 'latest' tag and the automated version tracking strategy. This addresses potential confusion about production version pinning.

Changes:

• Add "Image Versioning Strategy" section to README with rationale for using 'latest' tag and Chainguard images
• Document automated weekly version updates via GitHub Actions
• Provide alternative configuration for production version pinning
• Add Auto-Update and Chainguard badges to README header
• Include inline comments in values.yaml explaining image tag strategy
• Add table of contents entry for new documentation section