Merge the "release/v1.3.0+node24.15.0" branch into the "maintenance/v1+node24" branch

This merge promotes `release/v1.3.0+node24.15.0` into `maintenance/v1+node24`, marking the next minor release on the Node.js 24 maintenance line. It consolidates the Node.js base image bump from `24.14.1` to `24.15.0` and documentation updates aligning `README.md` and `CONTRIBUTING.md` with the new maintenance release state.

In `Dockerfile`, the builder stage base image is updated from `node:24.14.1-alpine3.23` to `node:24.15.0-alpine3.23`, bumping the bundled Node.js runtime from `24.14.1` to `24.15.0`. In `CONTRIBUTING.md`, the Node.js Version Bumps example is updated from `node:24.14.1-alpine3.23` to `node:24.15.0-alpine3.23`. In `README.md`, the Versioning and Tags example is updated from `v1.2.6+node24.14.1` to `v1.3.0+node24.15.0`, and the `docker/metadata-action` normalization note is updated from `v1.2.6+node24.14.1` → `v1.2.6-node24.14.1` to `v1.3.0+node24.15.0` → `v1.3.0-node24.15.0`.

No migration steps are required beyond updating to `v1.3.0+node24.15.0` on the `maintenance/v1+node24` line.

Author: Amnoor

CONTRIBUTING.md

@@ -78,7 +78,7 @@ All pull requests must:
 
 ## Node.js Version Bumps
 
-Node.js version upgrades are tracked as versioned releases. Requests must include the official Alpine Node image tag (for example, `node:24.14.1-alpine3.23`) and are expected to trigger a semver release bump for the image.
+Node.js version upgrades are tracked as versioned releases. Requests must include the official Alpine Node image tag (for example, `node:24.15.0-alpine3.23`) and are expected to trigger a semver release bump for the image.
 
 ## Documentation Standards
 

Dockerfile

@@ -1,6 +1,6 @@
 # Stage 1: Builder
 # Extract binaries, libraries, and generate configuration files.
-FROM node:24.14.1-alpine3.23 AS builder
+FROM node:24.15.0-alpine3.23 AS builder
 
 COPY --chmod=550 script.sh /
 COPY --chmod=550 dependencies/requirements.txt /dependencies/

README.md

@@ -175,12 +175,12 @@ Applications that need a different timezone can set `TZ` at runtime (timezone da
 ## Versioning and Tags
 
 Tags follow the pattern:
-- `v<major>.<minor>.<patch>+node<node_version>` (example: `v1.2.6+node24.14.1`)
+- `v<major>.<minor>.<patch>+node<node_version>` (example: `v1.3.0+node24.15.0`)
 - `latest` tracks the most recent release.
 
 Check the GitHub Releases page for the current tag and Node.js version.
 
-> Because of the `docker/metadata-action`, all tags with `+`, turns into `-` (example: GitHub Releases `v1.2.6+node24.14.1` then it becomes `v1.2.6-node24.14.1` in the Docker Hub and GitHub Container Registry)
+> Because of the `docker/metadata-action`, all tags with `+`, turns into `-` (example: GitHub Releases `v1.3.0+node24.15.0` then it becomes `v1.3.0-node24.15.0` in the Docker Hub and GitHub Container Registry)
 
 ## Security Posture