@radhya/mach 2.0.32 → 2.0.34
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -23
- package/dist/index.js +100 -100
- package/package.json +2 -3
- package/docs/ota-implementation-plan.md +0 -1004
package/README.md
CHANGED
|
@@ -36,7 +36,6 @@ mach build --platform android
|
|
|
36
36
|
| `mach build` | Start a cloud build (iOS / Android) |
|
|
37
37
|
| `mach maestro` | Queue managed Maestro tests for a build or artifact |
|
|
38
38
|
| `mach ota` | Setup, publish, list, rollback, and promote OTA updates |
|
|
39
|
-
| `mach update` | Deprecated alias for `mach ota publish` |
|
|
40
39
|
| `mach submit` | Submit to App Store or Google Play |
|
|
41
40
|
| `mach credentials` | Manage iOS certificates, provisioning profiles & Android keystores |
|
|
42
41
|
| `mach credentials:service` | Upload App Store Connect or Google Play service credentials |
|
|
@@ -131,11 +130,10 @@ Use the framework guide that matches your app. The command surface stays the sam
|
|
|
131
130
|
- [Bare React Native](docs/frameworks/react-native.md)
|
|
132
131
|
- [Expo](docs/frameworks/expo.md)
|
|
133
132
|
- [Flutter](docs/frameworks/flutter.md)
|
|
134
|
-
- [Mach OTA implementation plan](docs/ota-implementation-plan.md)
|
|
135
133
|
|
|
136
134
|
## OTA Updates
|
|
137
135
|
|
|
138
|
-
Mach OTA
|
|
136
|
+
Mach OTA lets you publish JavaScript and asset updates through Mach without using EAS Update. Mach hosts the update artifacts and serves the right update by channel, platform, and runtime version. Your app never needs storage credentials.
|
|
139
137
|
|
|
140
138
|
```bash
|
|
141
139
|
mach ota setup
|
|
@@ -150,26 +148,7 @@ For Expo apps, `mach ota setup` writes `ota` config and wires `@radhya/mach/expo
|
|
|
150
148
|
|
|
151
149
|
Command flags always win over config values. For example, `mach ota publish --channel staging --runtime-version 1.2.0` overrides `ota.channel` and `ota.runtimeVersion`.
|
|
152
150
|
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
```bash
|
|
156
|
-
OTA_STORAGE_PROVIDER=r2
|
|
157
|
-
CLOUDFLARE_R2_ACCOUNT_ID=...
|
|
158
|
-
CLOUDFLARE_R2_ACCESS_KEY_ID=...
|
|
159
|
-
CLOUDFLARE_R2_SECRET_ACCESS_KEY=...
|
|
160
|
-
CLOUDFLARE_R2_BUCKET=...
|
|
161
|
-
MACH_OTA_PUBLIC_URL=https://ota.getmach.dev
|
|
162
|
-
TABLE_UPDATES=MachUpdates
|
|
163
|
-
```
|
|
164
|
-
|
|
165
|
-
Create the DynamoDB table once from the Mach API project:
|
|
166
|
-
|
|
167
|
-
```bash
|
|
168
|
-
cd api
|
|
169
|
-
TABLE_UPDATES=MachUpdates npm run create:ota-table
|
|
170
|
-
```
|
|
171
|
-
|
|
172
|
-
Vanilla React Native uses the same API/R2/Dashboard backbone. The native OTA client and automatic native patching are intentionally guarded until the Mach RN client package is ready.
|
|
151
|
+
Vanilla React Native uses the same command surface. The native OTA client and automatic native patching are intentionally guarded until the Mach RN client package is ready.
|
|
173
152
|
|
|
174
153
|
## Deep Links
|
|
175
154
|
|