@spunto/build 0.17.0 → 0.18.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spunto/build",
-  "version": "0.17.0",
+  "version": "0.18.0",
   "description": "Spunto's shared Build engine — the devcontainer image protocol and VS Code extension registry clients, with no database, no HTTP framework and no UI.",
   "type": "module",
   "license": "MIT",

package/src/catalogs/index.ts

@@ -42,42 +42,63 @@ export type DevFeature = {
   defaultOptions?: Record<string, string>
 }
 
+/**
+ * The starter images, newest first. Refreshed on 2026-10-20 — Node 26 is the current release and
+ * becomes LTS this month, Node 24 the active LTS; Python 3.14, Go 1.27, Java 25 LTS, .NET 10 LTS,
+ * Ubuntu 24.04. Tags checked against `mcr.microsoft.com/v2/devcontainers/<image>/tags/list`.
+ *
+ * A project stores the image reference, never this id: dropping an entry here leaves the projects
+ * built on it working — they just show it as a custom image. On Spunto Cloud a catalog image with
+ * nothing added is a *starter* recipe whose build every org shares (`isSharedRecipe`, docs/onboarding.md).
+ */
 export const AVAILABLE_IMAGES: DevImage[] = [
   {
-    id: "typescript-node-20",
-    label: "Node.js 20 (TypeScript)",
-    image: "mcr.microsoft.com/devcontainers/typescript-node:20",
-    description: "Node.js 20 + TypeScript, npm/yarn/pnpm",
+    id: "typescript-node-26",
+    label: "Node.js 26 (TypeScript)",
+    image: "mcr.microsoft.com/devcontainers/typescript-node:26",
+    description: "Node.js 26 + TypeScript, npm/yarn/pnpm",
   },
   {
-    id: "javascript-node-20",
-    label: "Node.js 20 (JavaScript)",
-    image: "mcr.microsoft.com/devcontainers/javascript-node:20",
-    description: "Node.js 20, npm/yarn/pnpm",
+    id: "typescript-node-24",
+    label: "Node.js 24 LTS (TypeScript)",
+    image: "mcr.microsoft.com/devcontainers/typescript-node:24",
+    description: "Node.js 24 LTS + TypeScript, npm/yarn/pnpm",
   },
   {
-    id: "python-312",
-    label: "Python 3.12",
-    image: "mcr.microsoft.com/devcontainers/python:3.12",
-    description: "Python 3.12, pip, conda",
+    id: "python-314",
+    label: "Python 3.14",
+    image: "mcr.microsoft.com/devcontainers/python:3.14",
+    description: "Python 3.14, pip, pipx",
   },
   {
-    id: "go-121",
-    label: "Go 1.21",
-    image: "mcr.microsoft.com/devcontainers/go:1.21",
-    description: "Go 1.21, go tools",
+    id: "go-127",
+    label: "Go 1.27",
+    image: "mcr.microsoft.com/devcontainers/go:1.27",
+    description: "Go 1.27, gopls, delve",
   },
   {
     id: "rust",
     label: "Rust",
-    image: "mcr.microsoft.com/devcontainers/rust:latest",
-    description: "Rust stable, cargo",
+    image: "mcr.microsoft.com/devcontainers/rust:1",
+    description: "Rust stable, cargo, rust-analyzer",
+  },
+  {
+    id: "java-25",
+    label: "Java 25 LTS",
+    image: "mcr.microsoft.com/devcontainers/java:25",
+    description: "Java 25 (JDK), Maven, Gradle",
+  },
+  {
+    id: "dotnet-10",
+    label: ".NET 10 LTS",
+    image: "mcr.microsoft.com/devcontainers/dotnet:10.0",
+    description: ".NET 10 SDK, C#",
   },
   {
-    id: "java-21",
-    label: "Java 21",
-    image: "mcr.microsoft.com/devcontainers/java:21",
-    description: "Java 21 (JDK), Maven, Gradle",
+    id: "ubuntu-2404",
+    label: "Ubuntu 24.04",
+    image: "mcr.microsoft.com/devcontainers/base:noble",
+    description: "A bare Ubuntu 24.04 — bring your own toolchain",
   },
 ]
 

package/src/script/setup-script.ts

@@ -1132,10 +1132,15 @@ export function buildSetupScript(params: SetupScriptParams): { script: string }
   // `project.dind` makes DinD available without the docker-in-docker feature (baked into the base
   // image, see images/worker-base) — treat it like the feature for entrypoint start + docker wait.
   const hasDinDFeature = (project.features?.some((f) => f.id === "docker-in-docker") ?? false) || !!project.dind
+  // `_MP_EP_STARTED` tells the every-start block of the same run (buildWorkerScript inlines both in
+  // one shell) not to start them a second time: the docker-in-docker feature's entrypoint doesn't
+  // check for a running daemon, and a second dockerd fails on the volume store lock — after having
+  // replaced the first one's socket, leaving Docker unreachable for postStart and everything after.
   if (project.postCreateCommand && ((project.features && project.features.length > 0) || project.dind)) {
     push(
       "",
       "if [ -f " + FEATURE_ENTRYPOINTS_FILE + " ]; then",
+      "  _MP_EP_STARTED=1",
       '  echo "--- Starting feature entrypoints for postCreate ---"',
       "  while IFS= read -r _ep; do",
       '    if [ -f "$_ep" ]; then',
@@ -1299,9 +1304,11 @@ export function buildStartScript(params: StartScriptParams): { script: string; h
   }
 
   // ── 2. Feature entrypoints ────────────────────────────────────────────────
+  // Skipped when the first-start setup of this same run already started them for postCreate
+  // (`_MP_EP_STARTED`, see buildSetupScript §6).
   push(
     "",
-    "if [ -f " + FEATURE_ENTRYPOINTS_FILE + " ]; then",
+    "if [ -f " + FEATURE_ENTRYPOINTS_FILE + " ] && [ -z \"${_MP_EP_STARTED:-}\" ]; then",
     '  echo "--- Starting feature entrypoints ---"',
     "  while IFS= read -r _ep; do",
     '    if [ -f "$_ep" ]; then',