Web client version still shows 0.0.0 — app.json not stamped in the container build #291
Labels
No labels
area:auth
area:ci
area:db
area:infra
area:native
area:pwa
area:service
epic
feature
foundation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
james/carol#291
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #289 / PR #290.
The
v0.0.1-rc.16build (which does include #290) still shows the version as0.0.0in the web/PWA settings footer.Cause
PR #290's
release.ymlstamp step writes the tag version intoapps/api/package.jsonand the rootpackage.json, but notapps/client/app.json. The container build (Dockerfile) builds the web client bundle withpnpm -F @carol/client export:web(Dockerfile line ~79), which bakesapp.json'sexpo.versioninto the bundle. The settings footer reads that at runtime viaexpo-constants. Sinceapp.jsonwas never stamped, the web bundle shipsexpo.version: 0.0.0→ footer showsCarol 0.0.0.The server
/api/healthis correct (apps/api/package.jsonwas stamped), and the Android APK is correct (release-android.ymlstampsapp.jsonbefore prebuild). Only the web client version was missed — and on web the footer shows just the client version, so the user sees0.0.0.Fix
Extend
release.yml's "Stamp build version" step to also setapps/client/app.jsonexpo.version(string only —versionCodeis Android-only and handled byrelease-android.yml) beforedocker build.