@catladder/cli 0.0.0-next-1c65899f → 0.0.0-next-2b60440e

package/dist/bundles/runner-images/semantic-release/Dockerfile

@@ -1,24 +1,27 @@
 # job images are addressed by a content hash of this directory — the
 # build must be reproducible, so every dependency is pinned exactly.
-# (@semantic-release/changelog@7 went ESM-only and broke overnight under
-# the CJS semantic-release@19 while the hash claimed "unchanged".)
-FROM node:22-alpine
+# node:24 satisfies the newer plugins' engine requirements
+# (@semantic-release/git and @semantic-release/changelog need node >=24.15).
+FROM node:24-alpine
 
 RUN apk add --no-cache bash git git-lfs
 
 # add semantic release
-# NOTE: keep every plugin pinned to a major that is compatible with
-# semantic-release@19 (they declare `semantic-release` as a peer dependency).
-# Unpinned plugins drift to their latest major on image rebuild, which now
-# requires semantic-release>=20 and fails with "plugins configuration is invalid".
+# NOTE: pin every dependency exactly. These are the semantic-release@25 line
+# (all ESM — v25 loads plugins via dynamic import, so changelog@7/git@11 are
+# fine). Every plugin declares `semantic-release` as a peer dependency, so a
+# plugin major that outpaces the semantic-release major fails the release job
+# with "plugins configuration is invalid" — bump them together. Upstream
+# @semantic-release/git replaces the old panter fork; see
+# scripts/semanticRelease for why the commit message is hardcoded.
 RUN yarn global add \
-    semantic-release@19.0.5 \
+    semantic-release@25.0.8 \
     @semantic-release/commit-analyzer@13.0.1 \
     @semantic-release/release-notes-generator@14.1.1 \
-    https://github.com/panter/git.git#b4037626cc583d3e9f7995ea0604b23730d0a22e \
-    @semantic-release/changelog@6.0.3 \
-    @semantic-release/gitlab@9.5.1 \
-    @semantic-release/exec@6.0.3
+    @semantic-release/git@11.0.0 \
+    @semantic-release/changelog@7.0.0 \
+    @semantic-release/gitlab@13.3.3 \
+    @semantic-release/exec@7.1.0
 
 RUN mkdir -p /scripts
 COPY ./scripts/* /scripts/

package/dist/bundles/runner-images/semantic-release/scripts/semanticRelease

@@ -77,8 +77,17 @@ if [ ! -e .releaserc ]; then
     ],
     "@semantic-release/release-notes-generator",
     "@semantic-release/changelog",
+    # message prefix hardcoded to "release" on purpose. Ideally this would be
+    # "chore(\${branch.type})", but upstream @semantic-release/git passes the
+    # branch *name* (not the object) into the template, so \${branch.type} is
+    # never available (see https://github.com/semantic-release/git/pull/213,
+    # open/ignored since 2020 — the README documents branch.type but the code
+    # never wired it up; the old panter fork existed only to patch this). On the
+    # default branch branch.type is always "release", and the pipeline
+    # loop-prevention rule keys on the literal "chore(release)" prefix, so keep
+    # this literal. Don't "fix" it back to \${branch.type}.
     ["@semantic-release/git", {
-      "message": "chore(\${branch.type}): \${nextRelease.version}\n\n\${nextRelease.notes}"
+      "message": "chore(release): \${nextRelease.version}\n\n\${nextRelease.notes}"
     }]${PUBLISH_PLUGIN}
     ],
   "branches": [

package/dist/runner-images/semantic-release/Dockerfile

@@ -1,24 +1,27 @@
 # job images are addressed by a content hash of this directory — the
 # build must be reproducible, so every dependency is pinned exactly.
-# (@semantic-release/changelog@7 went ESM-only and broke overnight under
-# the CJS semantic-release@19 while the hash claimed "unchanged".)
-FROM node:22-alpine
+# node:24 satisfies the newer plugins' engine requirements
+# (@semantic-release/git and @semantic-release/changelog need node >=24.15).
+FROM node:24-alpine
 
 RUN apk add --no-cache bash git git-lfs
 
 # add semantic release
-# NOTE: keep every plugin pinned to a major that is compatible with
-# semantic-release@19 (they declare `semantic-release` as a peer dependency).
-# Unpinned plugins drift to their latest major on image rebuild, which now
-# requires semantic-release>=20 and fails with "plugins configuration is invalid".
+# NOTE: pin every dependency exactly. These are the semantic-release@25 line
+# (all ESM — v25 loads plugins via dynamic import, so changelog@7/git@11 are
+# fine). Every plugin declares `semantic-release` as a peer dependency, so a
+# plugin major that outpaces the semantic-release major fails the release job
+# with "plugins configuration is invalid" — bump them together. Upstream
+# @semantic-release/git replaces the old panter fork; see
+# scripts/semanticRelease for why the commit message is hardcoded.
 RUN yarn global add \
-    semantic-release@19.0.5 \
+    semantic-release@25.0.8 \
     @semantic-release/commit-analyzer@13.0.1 \
     @semantic-release/release-notes-generator@14.1.1 \
-    https://github.com/panter/git.git#b4037626cc583d3e9f7995ea0604b23730d0a22e \
-    @semantic-release/changelog@6.0.3 \
-    @semantic-release/gitlab@9.5.1 \
-    @semantic-release/exec@6.0.3
+    @semantic-release/git@11.0.0 \
+    @semantic-release/changelog@7.0.0 \
+    @semantic-release/gitlab@13.3.3 \
+    @semantic-release/exec@7.1.0
 
 RUN mkdir -p /scripts
 COPY ./scripts/* /scripts/

package/dist/runner-images/semantic-release/scripts/semanticRelease

@@ -77,8 +77,17 @@ if [ ! -e .releaserc ]; then
     ],
     "@semantic-release/release-notes-generator",
     "@semantic-release/changelog",
+    # message prefix hardcoded to "release" on purpose. Ideally this would be
+    # "chore(\${branch.type})", but upstream @semantic-release/git passes the
+    # branch *name* (not the object) into the template, so \${branch.type} is
+    # never available (see https://github.com/semantic-release/git/pull/213,
+    # open/ignored since 2020 — the README documents branch.type but the code
+    # never wired it up; the old panter fork existed only to patch this). On the
+    # default branch branch.type is always "release", and the pipeline
+    # loop-prevention rule keys on the literal "chore(release)" prefix, so keep
+    # this literal. Don't "fix" it back to \${branch.type}.
     ["@semantic-release/git", {
-      "message": "chore(\${branch.type}): \${nextRelease.version}\n\n\${nextRelease.notes}"
+      "message": "chore(release): \${nextRelease.version}\n\n\${nextRelease.notes}"
     }]${PUBLISH_PLUGIN}
     ],
   "branches": [

package/package.json

@@ -53,7 +53,7 @@
     }
   ],
   "license": "MIT",
-  "version": "0.0.0-next-1c65899f",
+  "version": "0.0.0-next-2b60440e",
   "scripts": {
     "lint": "eslint \"src/**/*.ts\"",
     "lint:fix": "eslint \"src/**/*.ts\" --fix",