Remove deprecated Ruby 3.2 variants from README and manifest files

[sireeshajonnalagadda]

Ruby 3.2 ended its support on 01-04-2026.
Ref-1464

[Copilot]

Pull request overview

Removes documentation and manifest entries for deprecated Ruby 3.2 image variants now that Ruby 3.2 is out of support, keeping published tags aligned with supported Ruby versions.

Changes:

• Removed Ruby 3.2 tag references from src/ruby/README.md.
• Removed 3.2-* entries from parts of src/ruby/manifest.json (architectures + variantTags).

Show a summary per file

File	Description
src/ruby/README.md	Updates published/available tag documentation to drop Ruby 3.2 references.
src/ruby/manifest.json	Removes some Ruby 3.2 build/tag metadata, intended to stop publishing 3.2 variants.

Copilot's findings

Comments suppressed due to low confidence (2)

src/ruby/manifest.json:36

• The Ruby 3.2 variants are still listed in the top-level variants array (e.g., 3.2-trixie, 3.2-bookworm, 3.2-bullseye), but their build.architectures and build.variantTags entries were removed in this PR. This leaves the manifest internally inconsistent and can break any tooling that iterates variants to build/publish tags. Remove the 3.2 entries from the variants array (and any other remaining 3.2 references in this manifest) so the manifest stays self-consistent.

This issue also appears on line 72 of the same file.

			],			
			"3.4-bookworm": [
				"linux/amd64",
				"linux/arm64"
			],			

src/ruby/manifest.json:75

• This PR removes published variants (Ruby 3.2), which is a breaking change for consumers who pin those tags. Per the repo’s image-versioning practice, please bump manifest.json's version using semantic versioning for this change and update any README examples that reference the old ${VERSION} (e.g., 3.0.3-...) to match the new version.

			"3.4-bookworm": [
				"ruby:${VERSION}-3.4-bookworm"
			],
			"3.3-bookworm": [

• Files reviewed: 2/2 changed files
• Comments generated: 1