Skip to content

fix(build): unbreak v0.48.0 release build — webui compile errors + PR-time guard#896

Merged
hsinatfootprintai merged 1 commit into
mainfrom
fix/webui-release-build-guard
Jul 3, 2026
Merged

fix(build): unbreak v0.48.0 release build — webui compile errors + PR-time guard#896
hsinatfootprintai merged 1 commit into
mainfrom
fix/webui-release-build-guard

Conversation

@hsinatfootprintai

Copy link
Copy Markdown
Contributor

Summary

make build-release (which runs a full next build with TypeScript type-checking) failed on the v0.48.0 tag with two genuine compile errors from #886, neither caught at PR time because no CI job builds the web UI at all:

  • ContainerListView.tsx destructured props omitted onSecurityClick even though it's declared in the props interface, used in the JSX, and already passed in by ContainerTopology.tsx — a straight typo.
  • PentestView.tsx called client.listPentestScanRuns(<limit>) as a bare number, but the method's first positional param is the optional containerName string, not limit — fixed both call sites to listPentestScanRuns(undefined, <limit>).

This is the same failure class as #884 (Windows cross-compile only caught at release time) — closed the same way #885 did: added the real next build as a step in the already-required "Unit + default e2e" job.

Test plan

  • npx tsc --noEmit clean
  • npm run build (full production build) succeeds
  • New CI step added mirrors the exact same job/precedent as the Windows guard

🤖 Generated with Claude Code

…-time guard

make build-release (which runs a full `next build` with TypeScript
type-checking) failed on the v0.48.0 tag:

- ContainerListView.tsx destructured props omitted onSecurityClick even
  though it's declared in the props interface, used in the JSX, and
  already passed in by ContainerTopology.tsx — a straight typo from #886.
- PentestView.tsx called client.listPentestScanRuns(<limit>) as a bare
  number, but the method's first positional param is the optional
  containerName string, not limit — passing a number there is a type
  error, not just a lint nit. Fixed both call sites to
  listPentestScanRuns(undefined, <limit>).

Neither was caught at PR time because no CI job builds the web UI at
all — the exact same "only surfaces at release time" gap as #884's
Windows cross-compile break, just for the web UI. Closes it the same
way #885 did: add the real `next build` as a step in the already-required
"Unit + default e2e" job, so a future TypeScript error fails the PR
instead of the release tag.
@hsinatfootprintai hsinatfootprintai merged commit 672f829 into main Jul 3, 2026
8 checks passed
@hsinatfootprintai hsinatfootprintai deleted the fix/webui-release-build-guard branch July 3, 2026 05:08
hsinatfootprintai added a commit that referenced this pull request Jul 3, 2026
v0.48.0's release build never published (webui compile errors, #896).
Stamps CHANGELOG ahead of the v0.48.1 tag, which supersedes it; v0.48.0
stays a dead tag rather than being retargeted.

Co-authored-by: hsinhoyeh <yhh92u@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants