Skip to content

fix(release): patch dev dependency and live validation fixtures - #1014

Merged
XiaoSeS merged 2 commits into
mainfrom
fix/github-sync-team-interop-contract-20261025
Oct 25, 2026
Merged

XiaoSeS merged 2 commits into
mainfrom
fix/github-sync-team-interop-contract-20261025

Conversation

@XiaoSeS

@XiaoSeS XiaoSeS commented Oct 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Patch the jsdom/Vitest development dependency chain from undici 7.30.0 to 7.30.1 using the existing pnpm override. No production dependency is added.
  • Correct the opt-in Go/Java live helper: its fixtures create TEAM sources, so they must not carry the platform-pause epoch reserved for @github. Exact task, repository, fixed commit and FULL-mode assertions are preserved.
  • Keep the interrupted-worker fixture's source and task repository IDs consistent when the real GitHub Tree API opt-in is enabled.
  • Give the explicitly enabled real Scanner a bounded 180-second completion budget while retaining 15 seconds for the HTTP fixture. Final version-state assertions still fail on timeout; production timeouts and business behavior are unchanged.

Validation

  • Node 24.17.0 / pnpm 10.33.0: frozen install, typecheck, lint, production build passed.
  • Frontend: 255 files / 1160 tests passed with --maxWorkers=2; no test reruns were needed for the dependency patch.
  • Official npm registry audit: zero advisories for the current Web lockfile. This does not claim all repository CodeQL findings are resolved.
  • Go 1.27.3: full package tests and vet passed; independent review also checked platform capability tests and formatting.
  • Real public GitHub data, Java 21, isolated PostgreSQL/Redis and the immutable candidate Scanner image: two live methods passed, zero failures/errors/skips (72.20 seconds), including a new cold Scanner container and the interrupt + real Tree combination.
  • Before the TEAM assertion correction, the minimal live method failed consistently; a boolean-only diagnostic confirmed the task/repository/commit/mode matched and only the incorrect epoch requirement failed.
  • The original 15-second real-Scanner failure and a subsequent external GitHub EOF are retained in the local validation evidence. The EOF happened before scanning; the successful rerun is not presented as if the first run passed.
  • No production server, domain route, database, tag or Release changed.

Commands include:

pnpm -C web install --frozen-lockfile
pnpm -C web typecheck
pnpm -C web lint
pnpm -C web test --maxWorkers=2
pnpm -C web build
pnpm -C web audit --registry=https://registry.npmjs.org --json
cd github-sync-go
GOTOOLCHAIN=go1.27.3 go test -count=1 -p 2 ./...
GOTOOLCHAIN=go1.27.3 go vet -p 2 ./...

The existing live integration methods were explicitly enabled with the fixed public archive fixture, real Tree API, external Scanner URL and interrupt opt-ins. Network-dependent checks remain separate from normal CI skips.

Risk

Only Web development dependencies and test fixtures change. No application API, database migration, scanner policy, worker protocol or production permission rule changes. The official platform-control contract remains unchanged. CI for this exact PR must pass before merge; Hong Kong deployment and release acceptance are separate gates.

Signed-off-by: XiaoSeS <87064762+XiaoSeS@users.noreply.github.com>
Signed-off-by: XiaoSeS <87064762+XiaoSeS@users.noreply.github.com>
@XiaoSeS
XiaoSeS merged commit 219dcca into main Oct 25, 2026
17 checks passed
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.

1 participant