(feat) Update prepare-release.sh to bump patch version in both manifest and README

Author: abdurriq

build/prepare-release.sh

@@ -38,6 +38,38 @@ bump_version() {
 	version=$(grep -oP '(?<="version": ")[^"]*' $manifestPath)
 	newVersion=$(echo $version | awk -F. -v OFS=. '{$NF += 1 ; print}')
 	sed -i "s/\"version\": \"$version\"/\"version\": \"$newVersion\"/g" $manifestPath
+	
+	# Also update version references in README.md
+	update_readme_version $directory $version $newVersion
+}
+
+update_readme_version() {
+	directory=$1
+	oldVersion=$2
+	newVersion=$3
+	readmePath="$directory/README.md"
+	
+	if [ ! -f "$readmePath" ]; then
+		echo "No README.md found at $readmePath, skipping README update"
+		return
+	fi
+	
+	# Extract major.minor from the version
+	majorMinor=$(echo $oldVersion | cut -d. -f1,2)
+	
+	# Check if major.minor version pattern exists in README
+	# Match :major.minor.patch followed by either - or ` (backtick) or end of word
+	if ! grep -qE ":${majorMinor}\.[0-9]+(-|\`)" "$readmePath"; then
+		echo "ERROR: Version pattern ${majorMinor}.x not found in $readmePath"
+		exit 1
+	fi
+	
+	# Update full version references (e.g., 1.3.x-variant -> 1.3.3-variant, or 1.3.x` -> 1.3.3`)
+	# The pattern matches major.minor.any_patch followed by - (variant) or ` (backtick)
+	sed -i "s/:${majorMinor}\.[0-9]*-/:${newVersion}-/g" $readmePath
+	sed -i "s/:${majorMinor}\.[0-9]*\`/:${newVersion}\`/g" $readmePath
+	
+	echo "Updated README.md version references from ${majorMinor}.x to $newVersion"
 }
 
 release_image() {

src/java/README.md

@@ -31,11 +31,11 @@ Refer to [this guide](https://containers.dev/guide/dockerfile) for more details.
 
 You can decide how often you want updates by referencing a [semantic version](https://semver.org/) of each image. For example:
 
-- `mcr.microsoft.com/devcontainers/java:2-11` (or `2-11-trixie`, `2-11-bookworm` to pin to an OS version)
-- `mcr.microsoft.com/devcontainers/java:2.0-11` (or `2.0-11-trixie`, `2.0-11-bookworm` to pin to an OS version)
-- `mcr.microsoft.com/devcontainers/java:2.0.0-11` (or `2.0.0-11-trixie`, `2.0.0-11-bookworm` to pin to an OS version)
+- `mcr.microsoft.com/devcontainers/java:3-11` (or `3-11-trixie`, `3-11-bookworm` to pin to an OS version)
+- `mcr.microsoft.com/devcontainers/java:3.0-11` (or `3.0-11-trixie`, `3.0-11-bookworm` to pin to an OS version)
+- `mcr.microsoft.com/devcontainers/java:3.0.5-11` (or `3.0.0-11-trixie`, `3.0.0-11-bookworm` to pin to an OS version)
 
-However, we only do security patching on the latest [non-breaking, in support](https://github.com/devcontainers/images/issues/90) versions of images (e.g. `2-11`). You may want to run `apt-get update && apt-get upgrade` in your Dockerfile if you lock to a more specific version to at least pick up OS security updates.
+However, we only do security patching on the latest [non-breaking, in support](https://github.com/devcontainers/images/issues/90) versions of images (e.g. `3-11`). You may want to run `apt-get update && apt-get upgrade` in your Dockerfile if you lock to a more specific version to at least pick up OS security updates.
 
 See [history](history) for information on the contents of each version and [here for a complete list of available tags](https://mcr.microsoft.com/v2/devcontainers/java/tags/list).
 

src/miniconda/README.md

@@ -29,8 +29,8 @@ Refer to [this guide](https://containers.dev/guide/dockerfile) for more details.
 You can decide how often you want updates by referencing a [semantic version](https://semver.org/) of each image. For example:
 
 - `mcr.microsoft.com/devcontainers/miniconda:1-3`
-- `mcr.microsoft.com/devcontainers/miniconda:1.0-3`
-- `mcr.microsoft.com/devcontainers/miniconda:1.0.0-3`
+- `mcr.microsoft.com/devcontainers/miniconda:1.1-3`
+- `mcr.microsoft.com/devcontainers/miniconda:1.1.0-3`
 
 See [history](history) for information on the contents of each version and [here for a complete list of available tags](https://mcr.microsoft.com/v2/devcontainers/miniconda/tags/list).