Release v3.8.9 — final sync (static-asset fix + contributor credits) by diegosouzapw · Pull Request #3135 · diegosouzapw/OmniRoute

diegosouzapw · 2026-06-04T07:22:54Z

Finalizes the v3.8.9 release for tagging. Brings the two commits that landed on `release/v3.8.9` after the initial release merge (#3092):

Included

fix(build): standalone static-asset path — `assembleStandalone` now copies `static/` (and `required-server-files.json` / Turbopack chunks) under the configured `distDir` (`.build/next/static`) instead of a hard-coded `.next`. Without this, the standalone server (built with `distDir=.build/next`) 404'd every JS/CSS chunk and the login UI rendered as a blank page after the build-output reorg. (`49dedecc4`)
docs(changelog): credit the 3 PRs merged directly to main during the v3.8.9 cycle and document the static fix:
- feat(kiro): add Claude Opus 4.8 to the Kiro model catalog #3131 Kiro Opus 4.8 catalog (thanks @artickc)
- Fix：Add KimiExecutor to fix the error of reasoning_content is missing in kimi thing mode #3132 Kimi thinking-mode `reasoning_content` fix (thanks @bypanghu)
- fix(handler): provide fallback for connectionId when undefined #3130 connectionId fallback + kilo call logging (thanks @androw)
- Contributors hall now lists all 15 contributors. (`796267df3`)

Validation

Static fix verified on the VM: built standalone serves chunks → HTTP 200, login UI renders.
Deployed + validated on the local VPS (192.168.0.15) by the maintainer.

After merge → tag `v3.8.9` → npm/docker/electron publishes.

…teral .next CRITICAL white-screen bug from the build-output-isolation refactor: the standalone server.js bakes distDir ("./.build/next") into its config and serves /_next/static from <root>/.build/next/static — but assembleStandalone hard-coded the destination to <outDir>/.next/static (+ sanitised/patched <outDir>/.next/{required-server-files, server}). Result: the server's static dir was EMPTY → every JS/CSS chunk 404'd → blank login page (health stayed 200, so it slipped past the health-only dry-run). Mirror the distDir path (relative to projectRoot) for static, required-server-files sanitization (was a silent no-op → 0 paths sanitised, now 11), and the Turbopack chunk patch. Verified: booting the assembled bundle serves the webpack chunk 200. Affects every consumer (npm/Docker/Electron/VPS).

@artickc

…ic-asset build fix - #3131 Kiro Opus 4.8 catalog (thanks @artickc) - #3132 Kimi thinking-mode reasoning_content fix (thanks @bypanghu) - #3130 connectionId fallback + kilo call logging (thanks @androw) - build: standalone static-asset path fix (white login screen after build-output reorg) - contributors hall: +@artickc +@bypanghu +@androw (15 total)

gemini-code-assist

Code Review

This pull request updates the standalone build assembly process to support custom build output directories (distDir) instead of assuming a hardcoded ".next" directory. It ensures static assets, required server files, and Turbopack chunks are correctly placed and referenced. The review feedback identifies edge cases where path resolution could fail if distDir is absolute or if the project root differs from the current working directory, offering robust code suggestions to normalize these paths.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

gemini-code-assist · 2026-06-04T07:24:30Z

+export function assemblePathSanitize(projectRoot, outDir, distDir = ".next") {
  const buildRoot = projectRoot.replace(/\\/g, "/"); // normalise for regex safety
  const sanitizeTargets = [
    path.join(outDir, "server.js"),
-    path.join(outDir, ".next", "required-server-files.json"),
+    // required-server-files.json lives under the distDir (e.g. .build/next), not
+    // a literal .next — the standalone preserves the configured distDir path.
+    path.join(outDir, distDir, "required-server-files.json"),
  ];


If distDir is passed as an absolute path, path.join(outDir, distDir, ...) will produce an incorrect path (e.g., outDir/absolute/path/...), causing fsSync.existsSync to fail and silently skipping the sanitization of required-server-files.json.

Since assemblePathSanitize has access to projectRoot, we can defensively normalize distDir to be relative to projectRoot if it is absolute.

Suggested change

export function assemblePathSanitize(projectRoot, outDir, distDir = ".next") {

const buildRoot = projectRoot.replace(/\\/g, "/"); // normalise for regex safety

const sanitizeTargets = [

path.join(outDir, "server.js"),

path.join(outDir, ".next", "required-server-files.json"),

// required-server-files.json lives under the distDir (e.g. .build/next), not

// a literal .next — the standalone preserves the configured distDir path.

path.join(outDir, distDir, "required-server-files.json"),

];

export function assemblePathSanitize(projectRoot, outDir, distDir = ".next") {

const buildRoot = projectRoot.replace(/\\/g, "/"); // normalise for regex safety

const relDistDir = path.isAbsolute(distDir) ? path.relative(projectRoot, distDir) : distDir;

const sanitizeTargets = [

path.join(outDir, "server.js"),

// required-server-files.json lives under the distDir (e.g. .build/next), not

// a literal .next — the standalone preserves the configured distDir path.

path.join(outDir, relDistDir, "required-server-files.json"),

];

gemini-code-assist · 2026-06-04T07:24:30Z

+  // The standalone bundle preserves the distDir path RELATIVE to projectRoot
+  // (the server's baked config uses e.g. "./.build/next"), so output dest paths
+  // for static / required-server-files / server chunks must use the relative
+  // distDir appended to outDir — never the absolute build-machine distDir.
+  const relDistDir = path.isAbsolute(distDir) ? path.relative(projectRoot, distDir) : distDir;
+
  const standaloneDir = path.resolve(path.join(distDir, "standalone"));


If distDir is relative and projectRoot is different from process.cwd(), path.resolve(path.join(distDir, "standalone")) will resolve against process.cwd() instead of projectRoot. This can lead to incorrect path resolution in monorepos or custom build environments.

We should resolve distDir against projectRoot first if it is relative, and then derive relDistDir and standaloneDir from it.

Suggested change

// The standalone bundle preserves the distDir path RELATIVE to projectRoot

// (the server's baked config uses e.g. "./.build/next"), so output dest paths

// for static / required-server-files / server chunks must use the relative

// distDir appended to outDir — never the absolute build-machine distDir.

const relDistDir = path.isAbsolute(distDir) ? path.relative(projectRoot, distDir) : distDir;

const standaloneDir = path.resolve(path.join(distDir, "standalone"));

// The standalone bundle preserves the distDir path RELATIVE to projectRoot

// (the server's baked config uses e.g. "./.build/next"), so output dest paths

// for static / required-server-files / server chunks must use the relative

// distDir appended to outDir — never the absolute build-machine distDir.

const resolvedDistDir = path.isAbsolute(distDir) ? distDir : path.resolve(projectRoot, distDir);

const relDistDir = path.relative(projectRoot, resolvedDistDir);

const standaloneDir = path.join(resolvedDistDir, "standalone");

gemini-code-assist · 2026-06-04T07:24:30Z

  const staticSrc = path.join(distDir, "static");
-  const staticDest = path.join(resolvedOutDir, ".next", "static");
+  const staticDest = path.join(resolvedOutDir, relDistDir, "static");


To ensure correct path resolution when projectRoot is different from process.cwd() and distDir is relative, staticSrc should be resolved using resolvedDistDir instead of distDir.

Suggested change

const staticSrc = path.join(distDir, "static");

const staticDest = path.join(resolvedOutDir, ".next", "static");

const staticDest = path.join(resolvedOutDir, relDistDir, "static");

const staticSrc = path.join(resolvedDistDir, "static");

const staticDest = path.join(resolvedOutDir, relDistDir, "static");

github-actions · 2026-06-04T07:34:04Z

CI Coverage Report

Coverage job: success
PR test policy: success

Coverage artifact was not available for this run.

…rCloud gate) Extract patchStandalonePackageJson / copyStaticAndPublic / copyNativeAssetsAndExtraModules helpers so assembleStandalone drops from cognitive complexity 29 → ~12 (≤15 gate). Also: replaceAll over replace, String.raw for the regex-escape replacement (2 minor smells). Pure refactor — assemble-standalone.test.ts still green; no behavior change.

sonarqubecloud · 2026-06-04T08:05:10Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

kilo-code-bot · 2026-06-04T08:09:02Z

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

CHANGELOG.md
scripts/build/assembleStandalone.mjs
tests/unit/build/assemble-standalone.test.ts

_{Reviewed by nemotron-3-super-120b-a12b-20230311:free · 1,845,266 tokens}

Release v3.8.9 — final sync (static-asset fix + contributor credits)

diegosouzapw added 2 commits June 4, 2026 02:17

gemini-code-assist Bot reviewed Jun 4, 2026

View reviewed changes

diegosouzapw merged commit 5057454 into main Jun 4, 2026
91 checks passed

HouMinXi pushed a commit to HouMinXi/OmniRoute that referenced this pull request Aug 2, 2026

Merge pull request diegosouzapw#3135 from diegosouzapw/release/v3.8.9

d99e407

Release v3.8.9 — final sync (static-asset fix + contributor credits)

Poid-ZA pushed a commit to Poid-ZA/OmniRoute that referenced this pull request Aug 5, 2026

Merge pull request diegosouzapw#3135 from diegosouzapw/release/v3.8.9

0e99e99

Release v3.8.9 — final sync (static-asset fix + contributor credits)

muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026

Merge pull request diegosouzapw#3135 from diegosouzapw/release/v3.8.9

416529c

Release v3.8.9 — final sync (static-asset fix + contributor credits)

Navigation Menu

Uh oh!

Release v3.8.9 — final sync (static-asset fix + contributor credits) - #3135

Release v3.8.9 — final sync (static-asset fix + contributor credits)#3135
diegosouzapw merged 3 commits into
mainfrom
release/v3.8.9

diegosouzapw commented Jun 4, 2026

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

gemini-code-assist Bot Jun 4, 2026

Uh oh!

gemini-code-assist Bot Jun 4, 2026

Uh oh!

gemini-code-assist Bot Jun 4, 2026

Uh oh!

github-actions Bot commented Jun 4, 2026

Uh oh!

sonarqubecloud Bot commented Jun 4, 2026

Uh oh!

kilo-code-bot Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

diegosouzapw commented Jun 4, 2026

Included

Validation

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Jun 4, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Jun 4, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Jun 4, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Jun 4, 2026

CI Coverage Report

Uh oh!

sonarqubecloud Bot commented Jun 4, 2026

Quality Gate passed

Uh oh!

kilo-code-bot Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Summary

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

kilo-code-bot Bot commented Jun 4, 2026 •

edited

Loading