You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ci): restore multi-arch Docker builds by adding platform to matrix
The `include` entries for linux/amd64 and linux/arm64 were not
cross-producted with the stack list, resulting in only one build
job per stack instead of two.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .planning/ROADMAP.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,12 @@ Plans:
55
55
2. Running the image against a bare RN repo produces a pre-upgrade audit report of native modules against New Architecture compatibility before any package version is changed
56
56
3. Running the image against a bare RN repo with `TARGET_RN=0.77` produces a branch where `react-native upgrade` has run, Gradle and AGP versions match the target release, and `./gradlew assembleDebug` exits 0 (when `ANDROID_BUILD=true`)
57
57
4.`verify-fast.sh` for RN includes a `./gradlew --version` check that catches Gradle/AGP version mismatch
**Goal**: All four new stacks are discoverable and launchable via the `stack-upgrade` CLI, and the CI pipeline builds and publishes both new Docker images on every release
@@ -81,18 +81,21 @@ Recent decisions affecting current work:
81
81
-[Phase 02-web-js-agent-templates]: REACT_APP_ documented as BUILD BLOCKER in CRA CLAUDE.md — viject does not rewrite these, agent must do it manually in Phase 2
82
82
-[Phase 02-web-js-agent-templates]: Jest-to-Vitest is Phase 8 (last) in CRA migration — Jest kept as safety net throughout build migration phases 1-7
83
83
-[Phase 02-web-js-agent-templates]: CI/CD REACT_APP_ references flagged but NOT modified by CRA agent — documented for human maintainer review only
84
+
-[Phase 02-web-js-agent-templates]: UnsafeUnwrapped and @next/codemod markers are BUILD BLOCKERS in Next.js CLAUDE.md — verify-fast.sh exits non-zero on them
85
+
-[Phase 02-web-js-agent-templates]: Next.js middleware/proxy uses next build + curl smoke test for Edge runtime verification — not Jest/Vitest (incompatible)
86
+
-[Phase 02-web-js-agent-templates]: entrypoint.sh nextjs) case fetches version-specific URL (version-N) when TARGET_NEXTJS set, falls back to generic URL
84
87
85
88
### Pending Todos
86
89
87
90
None yet.
88
91
89
92
### Blockers/Concerns
90
93
91
-
-[Phase 2] Next.js middleware verification without integration tests is unresolved — middleware runs at Edge runtime, not testable with Jest/Vitest. Approach: next build check + curl against next start. Validate during Phase 2 template design.
94
+
-[Phase 2] Next.js middleware verification RESOLVED — Middleware Verification Note in CLAUDE.md documents: use next build + curl against next start for smoke testing; if next start unavailable, document in run-log.md and rely on next build for static validation only.
92
95
-[Phase 3] React Native Upgrade Helper programmatic access (web UI vs rn-diff-purge raw data vs embedded diff) is unresolved. Address during Phase 3 planning.
0 commit comments