Repository navigation
Release 2.0.0 as a live update - #300
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
24f13d8 to
1e02dda
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Map the third live update on the 1.14.1 build 30 binary (production-30, live:1.14.1-ota.3) to a What's New announcement displayed as 2.0.0, and update the release guard, announcement tests and deployment guide. Native and package versions stay at 1.14.1 build 30 because this ships over the air.
e6a4af5 to
0b4b711
Compare
Summary
Prepares the design language overhaul (#299) to ship as 2.0.0 over the air through Capawesome, not as a store release.
live:1.14.1-ota.3. The About screen and the What's New dialog show 2.0.0 for that bundle.live:1.14.1-ota.2mapped to 1.15.0 and the native key mapped to 1.14.1.docs/deployment.md. The next store release must use a version above 2.0.0.Notes
package.json,package-lock.json, AndroidversionName/versionCodeand iOSMARKETING_VERSION/CURRENT_PROJECT_VERSIONstay at 1.14.1 build 30. An OTA targets the installed binary, so changing them would break theproduction-30channel.LIVE_UPDATE_CHANNEL="production-30" VITE_RELEASE_KEY="live:1.14.1-ota.3" npm run live-updateonce this is merged. No live update has been pushed.