Enhance bundling process in release script to resolve workspace package imports

Author: m-houston

packages/ddb-publisher/scripts/bundle-release.mjs

@@ -20,8 +20,6 @@ const outFile = resolve(outDir, "index.cjs");
 await rm(outDir, { recursive: true, force: true });
 await mkdir(dirname(outFile), { recursive: true });
 
-// Ensure generated workspace packages (notably the schemas package) have been created
-// before bundling. In CI, `npm ci` alone isn't enough.
 await esbuild.build({
   absWorkingDir: repoRoot,
   entryPoints: [resolve(packageRoot, "src/cli.ts")],
@@ -42,6 +40,12 @@ await esbuild.build({
   define: {
     "import.meta.url": "globalThis.__IMPORT_META_URL__",
   },
+  alias: {
+    // In CI, the workspace package may not be built/linked into node_modules.
+    // Alias it directly to the workspace directory so esbuild can resolve both
+    // package-root imports and deep imports under `src/**`.
+    "@nhsdigital/nhs-notify-event-schemas-supplier-config": "./packages/events",
+  },
 });
 
 // Add a small marker file to make the tarball contents obvious when debugging.