@marktiderman/genesis-cli 1.22.1 → 1.23.0
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/dist/genesis-catalog.json +11 -11
- package/dist/starter/.eas/workflows/deploy-production.yml +41 -38
- package/dist/starter/.eas/workflows/rollout.yml +3 -2
- package/dist/starter/README.md +2 -2
- package/dist/templates/eas/workflows/deploy-production.yml +41 -38
- package/dist/templates/eas/workflows/rollout.yml +3 -2
- package/package.json +1 -1
|
@@ -35,7 +35,7 @@
|
|
|
35
35
|
"version": "0.1.2"
|
|
36
36
|
},
|
|
37
37
|
"@marktiderman/genesis-chat": {
|
|
38
|
-
"version": "0.10.
|
|
38
|
+
"version": "0.10.1",
|
|
39
39
|
"blocks": {
|
|
40
40
|
"chat": {
|
|
41
41
|
"feature": {
|
|
@@ -111,7 +111,7 @@
|
|
|
111
111
|
"version": "2.13.0"
|
|
112
112
|
},
|
|
113
113
|
"@marktiderman/genesis-design-system": {
|
|
114
|
-
"version": "1.
|
|
114
|
+
"version": "1.10.0"
|
|
115
115
|
},
|
|
116
116
|
"@marktiderman/genesis-extension": {
|
|
117
117
|
"version": "0.2.2"
|
|
@@ -123,7 +123,7 @@
|
|
|
123
123
|
"version": "0.11.1"
|
|
124
124
|
},
|
|
125
125
|
"@marktiderman/genesis-forms-builder": {
|
|
126
|
-
"version": "0.6.
|
|
126
|
+
"version": "0.6.7"
|
|
127
127
|
},
|
|
128
128
|
"@marktiderman/genesis-forms-devtools": {
|
|
129
129
|
"version": "0.1.4"
|
|
@@ -135,16 +135,16 @@
|
|
|
135
135
|
"version": "0.3.3"
|
|
136
136
|
},
|
|
137
137
|
"@marktiderman/genesis-forms-studio": {
|
|
138
|
-
"version": "0.6.
|
|
138
|
+
"version": "0.6.4"
|
|
139
139
|
},
|
|
140
140
|
"@marktiderman/genesis-forms-web": {
|
|
141
|
-
"version": "0.8.
|
|
141
|
+
"version": "0.8.1"
|
|
142
142
|
},
|
|
143
143
|
"@marktiderman/genesis": {
|
|
144
|
-
"version": "0.10.
|
|
144
|
+
"version": "0.10.19"
|
|
145
145
|
},
|
|
146
146
|
"@marktiderman/genesis-cli": {
|
|
147
|
-
"version": "1.
|
|
147
|
+
"version": "1.23.0"
|
|
148
148
|
},
|
|
149
149
|
"@marktiderman/genesis-media": {
|
|
150
150
|
"version": "0.2.0"
|
|
@@ -423,7 +423,7 @@
|
|
|
423
423
|
}
|
|
424
424
|
},
|
|
425
425
|
"@marktiderman/genesis-sites": {
|
|
426
|
-
"version": "0.6.
|
|
426
|
+
"version": "0.6.1",
|
|
427
427
|
"blocks": {
|
|
428
428
|
"sites": {
|
|
429
429
|
"feature": {
|
|
@@ -712,7 +712,7 @@
|
|
|
712
712
|
}
|
|
713
713
|
},
|
|
714
714
|
"@marktiderman/genesis-support": {
|
|
715
|
-
"version": "0.6.
|
|
715
|
+
"version": "0.6.1",
|
|
716
716
|
"blocks": {
|
|
717
717
|
"support-feedback": {
|
|
718
718
|
"feature": {
|
|
@@ -1023,10 +1023,10 @@
|
|
|
1023
1023
|
"version": "2.1.3"
|
|
1024
1024
|
},
|
|
1025
1025
|
"@marktiderman/genesis-ui": {
|
|
1026
|
-
"version": "2.32.
|
|
1026
|
+
"version": "2.32.1"
|
|
1027
1027
|
},
|
|
1028
1028
|
"@marktiderman/genesis-ui-native": {
|
|
1029
|
-
"version": "3.9.
|
|
1029
|
+
"version": "3.9.1"
|
|
1030
1030
|
}
|
|
1031
1031
|
}
|
|
1032
1032
|
}
|
|
@@ -1,30 +1,32 @@
|
|
|
1
|
-
# Deploy to production
|
|
2
|
-
#
|
|
3
|
-
# the same change. The version isn't part of the fingerprint, so a bump on its own starts no
|
|
4
|
-
# build, and a native change without one uploads the old version string again.
|
|
1
|
+
# Deploy to production on every merge to main. main is protected (pull requests only, and only the
|
|
2
|
+
# people allowed to merge into it), so that merge is the release's approval.
|
|
5
3
|
#
|
|
6
4
|
# 1. Fingerprint the native project as the production variant builds it.
|
|
7
5
|
# 2. Per platform, look for a production build with that fingerprint.
|
|
8
|
-
# -
|
|
9
|
-
#
|
|
10
|
-
# -
|
|
11
|
-
#
|
|
6
|
+
# - One exists (JavaScript only): publish an over-the-air update to the `production` channel, to
|
|
7
|
+
# every install.
|
|
8
|
+
# - None (native code changed): build one and submit it in the same run. Installs can't take an
|
|
9
|
+
# update across a native change, so the new code reaches phones through the new build.
|
|
10
|
+
#
|
|
11
|
+
# A merge that changes native code is a new store version once it's released: bump `version` in
|
|
12
|
+
# app.config.ts in the same change when you mean to release it. The build number goes up by itself
|
|
13
|
+
# (eas.json autoIncrement).
|
|
12
14
|
#
|
|
13
15
|
# Safety:
|
|
14
|
-
# - A
|
|
15
|
-
#
|
|
16
|
-
#
|
|
17
|
-
# -
|
|
18
|
-
#
|
|
19
|
-
#
|
|
16
|
+
# - A push to main is the only trigger, so a run always builds a commit in git, never a local
|
|
17
|
+
# folder. `eas workflow:run` can start it anyway (and without `--ref` uploads the working
|
|
18
|
+
# directory), so the first job runs only for a push to main and a manual run does nothing.
|
|
19
|
+
# - Runs are serialized (`concurrency`): two quick merges never publish out of order.
|
|
20
|
+
# - Updates go to every install, not a staged share: EAS refuses a second rollout on the same
|
|
21
|
+
# channel, platform and runtime while one is in progress, so a staged update would make the next
|
|
22
|
+
# merge's update fail. To take one back, republish the update before it
|
|
23
|
+
# (`eas update:republish --group <id>`); rollout.yml does that for a staged one.
|
|
24
|
+
# - A build is submitted in the same run that made it, so an update never goes to a production
|
|
25
|
+
# build that nobody has. If a submit fails, submit that build by hand before the next merge
|
|
26
|
+
# (`eas submit --platform ios --id <build id> --profile production`).
|
|
20
27
|
# - Builds go to TestFlight and to the Play internal track as a draft (eas.json `submit`);
|
|
21
28
|
# releasing to the stores stays a person's step in App Store Connect and Play Console.
|
|
22
|
-
# -
|
|
23
|
-
# in progress, so a new update can't silently replace a staged one (finish it with rollout.yml).
|
|
24
|
-
# - Each platform's update is its own update group; promote or roll back each with rollout.yml.
|
|
25
|
-
# - A production build whose approval was rejected (or whose submit failed) still matches its
|
|
26
|
-
# fingerprint: a later JavaScript-only tag sends an update to a binary nobody has. Submit that
|
|
27
|
-
# build by hand first (`eas submit --platform ios --id <build id> --profile production`).
|
|
29
|
+
# - Each platform's build or update is its own: a failure on one doesn't hold the other back.
|
|
28
30
|
#
|
|
29
31
|
# Genesis template (templates/eas/workflows/deploy-production.yml). Edit the copy in your app; see
|
|
30
32
|
# docs/NATIVE-RELEASE.md in the Genesis repository.
|
|
@@ -32,11 +34,19 @@ name: Deploy production
|
|
|
32
34
|
|
|
33
35
|
on:
|
|
34
36
|
push:
|
|
35
|
-
|
|
37
|
+
branches: [main]
|
|
38
|
+
|
|
39
|
+
# One deploy at a time. The running one always finishes (no cancel_in_progress); the newest merge
|
|
40
|
+
# waits for it and EAS drops the runs in between, so an older merge never publishes last.
|
|
41
|
+
concurrency:
|
|
42
|
+
group: ${{ workflow.filename }}-${{ github.ref }}
|
|
36
43
|
|
|
37
44
|
jobs:
|
|
38
45
|
fingerprint:
|
|
39
46
|
name: Fingerprint
|
|
47
|
+
# Only a push to main. `eas workflow:run` starts any workflow whatever its `on` says, and
|
|
48
|
+
# without --ref it uploads a local folder; skipping here skips every job after it.
|
|
49
|
+
if: ${{ github.event_name == 'push' && github.ref_name == 'main' }}
|
|
40
50
|
type: fingerprint
|
|
41
51
|
environment: production
|
|
42
52
|
env:
|
|
@@ -83,18 +93,9 @@ jobs:
|
|
|
83
93
|
platform: android
|
|
84
94
|
profile: production
|
|
85
95
|
|
|
86
|
-
approve_release:
|
|
87
|
-
name: Approve submitting the builds and publishing the updates
|
|
88
|
-
# Both lookups must have succeeded (needs) and neither build failed (after): a failure on one
|
|
89
|
-
# platform never leaves the other to ship alone.
|
|
90
|
-
needs: [get_ios_build, get_android_build]
|
|
91
|
-
after: [build_ios, build_android]
|
|
92
|
-
if: ${{ after.build_ios.status != 'failure' && after.build_android.status != 'failure' }}
|
|
93
|
-
type: require-approval
|
|
94
|
-
|
|
95
96
|
submit_ios:
|
|
96
97
|
name: Submit iOS to TestFlight
|
|
97
|
-
needs: [build_ios
|
|
98
|
+
needs: [build_ios]
|
|
98
99
|
if: ${{ needs.build_ios.outputs.build_id }}
|
|
99
100
|
type: submit
|
|
100
101
|
environment: production
|
|
@@ -104,7 +105,7 @@ jobs:
|
|
|
104
105
|
|
|
105
106
|
submit_android:
|
|
106
107
|
name: Submit Android to the internal track (draft)
|
|
107
|
-
needs: [build_android
|
|
108
|
+
needs: [build_android]
|
|
108
109
|
if: ${{ needs.build_android.outputs.build_id }}
|
|
109
110
|
type: submit
|
|
110
111
|
environment: production
|
|
@@ -113,8 +114,8 @@ jobs:
|
|
|
113
114
|
profile: production
|
|
114
115
|
|
|
115
116
|
update_ios:
|
|
116
|
-
name: Update iOS (
|
|
117
|
-
needs: [get_ios_build
|
|
117
|
+
name: Update iOS (every production install)
|
|
118
|
+
needs: [get_ios_build]
|
|
118
119
|
if: ${{ needs.get_ios_build.outputs.build_id }}
|
|
119
120
|
type: update
|
|
120
121
|
environment: production
|
|
@@ -124,15 +125,16 @@ jobs:
|
|
|
124
125
|
params:
|
|
125
126
|
channel: production
|
|
126
127
|
platform: ios
|
|
127
|
-
rollout_percentage:
|
|
128
|
+
# No rollout_percentage: unset, the update goes to every install. Set to 100, EAS published
|
|
129
|
+
# it as a rollout and a consumer app's update job failed ("GraphQL request failed").
|
|
128
130
|
# Explicit: unset, EAS tries a Sentry source map upload whenever @sentry/react-native is
|
|
129
131
|
# installed and only logs a failure. Set true once the Sentry plugin is on in app.config.ts
|
|
130
132
|
# (with SENTRY_AUTH_TOKEN), so a failed upload fails the job.
|
|
131
133
|
upload_sentry_sourcemaps: false
|
|
132
134
|
|
|
133
135
|
update_android:
|
|
134
|
-
name: Update Android (
|
|
135
|
-
needs: [get_android_build
|
|
136
|
+
name: Update Android (every production install)
|
|
137
|
+
needs: [get_android_build]
|
|
136
138
|
if: ${{ needs.get_android_build.outputs.build_id }}
|
|
137
139
|
type: update
|
|
138
140
|
environment: production
|
|
@@ -142,7 +144,8 @@ jobs:
|
|
|
142
144
|
params:
|
|
143
145
|
channel: production
|
|
144
146
|
platform: android
|
|
145
|
-
rollout_percentage:
|
|
147
|
+
# No rollout_percentage: unset, the update goes to every install. Set to 100, EAS published
|
|
148
|
+
# it as a rollout and a consumer app's update job failed ("GraphQL request failed").
|
|
146
149
|
# Explicit: unset, EAS tries a Sentry source map upload whenever @sentry/react-native is
|
|
147
150
|
# installed and only logs a failure. Set true once the Sentry plugin is on in app.config.ts
|
|
148
151
|
# (with SENTRY_AUTH_TOKEN), so a failed upload fails the job.
|
|
@@ -1,4 +1,5 @@
|
|
|
1
|
-
# Promote or roll back a staged production update
|
|
1
|
+
# Promote or roll back a staged production update: one published by hand with `--rollout-percentage`
|
|
2
|
+
# (deploy-production.yml sends every merge's update to every install).
|
|
2
3
|
#
|
|
3
4
|
# Run it by hand, from git:
|
|
4
5
|
#
|
|
@@ -40,7 +41,7 @@ on:
|
|
|
40
41
|
update_group_id:
|
|
41
42
|
type: string
|
|
42
43
|
required: true
|
|
43
|
-
description: One platform's update group
|
|
44
|
+
description: One platform's update group you published by hand with `--rollout-percentage` (`eas update:list --branch production`). deploy-production.yml publishes at 100%, which has no rollout to promote or roll back.
|
|
44
45
|
action:
|
|
45
46
|
type: choice
|
|
46
47
|
required: true
|
package/dist/starter/README.md
CHANGED
|
@@ -239,8 +239,8 @@ flows; [docs/NATIVE-RELEASE.md](../../docs/NATIVE-RELEASE.md) has the setup and
|
|
|
239
239
|
| --- | --- | --- |
|
|
240
240
|
| `pr-preview.yml` | a pull request into `main` that changes the app, or one labeled `Preview` | Repack a preview build with the same fingerprint (or build one), publish an update to `pr-<number>`, comment the install link and QR code. iOS once `PREVIEW_IOS=true`. |
|
|
241
241
|
| `e2e.yml` | by hand (Maestro needs a paid EAS plan) | The Maestro flows on an iOS simulator build. |
|
|
242
|
-
| `deploy-production.yml` |
|
|
243
|
-
| `rollout.yml` | by hand | Promote
|
|
242
|
+
| `deploy-production.yml` | every merge to `main` | A store build (submitted in the same run) where native code changed, else an update to every `production` install. |
|
|
243
|
+
| `rollout.yml` | by hand | Promote an update you staged by hand after a failed-launch check, or roll it back. |
|
|
244
244
|
|
|
245
245
|
Profiles: `development`, `preview` and `production` build the `APP_VARIANT` of the same name on
|
|
246
246
|
the channel of the same name; `e2e` is a development build for the simulator. Store ids in
|
|
@@ -1,30 +1,32 @@
|
|
|
1
|
-
# Deploy to production
|
|
2
|
-
#
|
|
3
|
-
# the same change. The version isn't part of the fingerprint, so a bump on its own starts no
|
|
4
|
-
# build, and a native change without one uploads the old version string again.
|
|
1
|
+
# Deploy to production on every merge to main. main is protected (pull requests only, and only the
|
|
2
|
+
# people allowed to merge into it), so that merge is the release's approval.
|
|
5
3
|
#
|
|
6
4
|
# 1. Fingerprint the native project as the production variant builds it.
|
|
7
5
|
# 2. Per platform, look for a production build with that fingerprint.
|
|
8
|
-
# -
|
|
9
|
-
#
|
|
10
|
-
# -
|
|
11
|
-
#
|
|
6
|
+
# - One exists (JavaScript only): publish an over-the-air update to the `production` channel, to
|
|
7
|
+
# every install.
|
|
8
|
+
# - None (native code changed): build one and submit it in the same run. Installs can't take an
|
|
9
|
+
# update across a native change, so the new code reaches phones through the new build.
|
|
10
|
+
#
|
|
11
|
+
# A merge that changes native code is a new store version once it's released: bump `version` in
|
|
12
|
+
# app.config.ts in the same change when you mean to release it. The build number goes up by itself
|
|
13
|
+
# (eas.json autoIncrement).
|
|
12
14
|
#
|
|
13
15
|
# Safety:
|
|
14
|
-
# - A
|
|
15
|
-
#
|
|
16
|
-
#
|
|
17
|
-
# -
|
|
18
|
-
#
|
|
19
|
-
#
|
|
16
|
+
# - A push to main is the only trigger, so a run always builds a commit in git, never a local
|
|
17
|
+
# folder. `eas workflow:run` can start it anyway (and without `--ref` uploads the working
|
|
18
|
+
# directory), so the first job runs only for a push to main and a manual run does nothing.
|
|
19
|
+
# - Runs are serialized (`concurrency`): two quick merges never publish out of order.
|
|
20
|
+
# - Updates go to every install, not a staged share: EAS refuses a second rollout on the same
|
|
21
|
+
# channel, platform and runtime while one is in progress, so a staged update would make the next
|
|
22
|
+
# merge's update fail. To take one back, republish the update before it
|
|
23
|
+
# (`eas update:republish --group <id>`); rollout.yml does that for a staged one.
|
|
24
|
+
# - A build is submitted in the same run that made it, so an update never goes to a production
|
|
25
|
+
# build that nobody has. If a submit fails, submit that build by hand before the next merge
|
|
26
|
+
# (`eas submit --platform ios --id <build id> --profile production`).
|
|
20
27
|
# - Builds go to TestFlight and to the Play internal track as a draft (eas.json `submit`);
|
|
21
28
|
# releasing to the stores stays a person's step in App Store Connect and Play Console.
|
|
22
|
-
# -
|
|
23
|
-
# in progress, so a new update can't silently replace a staged one (finish it with rollout.yml).
|
|
24
|
-
# - Each platform's update is its own update group; promote or roll back each with rollout.yml.
|
|
25
|
-
# - A production build whose approval was rejected (or whose submit failed) still matches its
|
|
26
|
-
# fingerprint: a later JavaScript-only tag sends an update to a binary nobody has. Submit that
|
|
27
|
-
# build by hand first (`eas submit --platform ios --id <build id> --profile production`).
|
|
29
|
+
# - Each platform's build or update is its own: a failure on one doesn't hold the other back.
|
|
28
30
|
#
|
|
29
31
|
# Genesis template (templates/eas/workflows/deploy-production.yml). Edit the copy in your app; see
|
|
30
32
|
# docs/NATIVE-RELEASE.md in the Genesis repository.
|
|
@@ -32,11 +34,19 @@ name: Deploy production
|
|
|
32
34
|
|
|
33
35
|
on:
|
|
34
36
|
push:
|
|
35
|
-
|
|
37
|
+
branches: [main]
|
|
38
|
+
|
|
39
|
+
# One deploy at a time. The running one always finishes (no cancel_in_progress); the newest merge
|
|
40
|
+
# waits for it and EAS drops the runs in between, so an older merge never publishes last.
|
|
41
|
+
concurrency:
|
|
42
|
+
group: ${{ workflow.filename }}-${{ github.ref }}
|
|
36
43
|
|
|
37
44
|
jobs:
|
|
38
45
|
fingerprint:
|
|
39
46
|
name: Fingerprint
|
|
47
|
+
# Only a push to main. `eas workflow:run` starts any workflow whatever its `on` says, and
|
|
48
|
+
# without --ref it uploads a local folder; skipping here skips every job after it.
|
|
49
|
+
if: ${{ github.event_name == 'push' && github.ref_name == 'main' }}
|
|
40
50
|
type: fingerprint
|
|
41
51
|
environment: production
|
|
42
52
|
env:
|
|
@@ -83,18 +93,9 @@ jobs:
|
|
|
83
93
|
platform: android
|
|
84
94
|
profile: production
|
|
85
95
|
|
|
86
|
-
approve_release:
|
|
87
|
-
name: Approve submitting the builds and publishing the updates
|
|
88
|
-
# Both lookups must have succeeded (needs) and neither build failed (after): a failure on one
|
|
89
|
-
# platform never leaves the other to ship alone.
|
|
90
|
-
needs: [get_ios_build, get_android_build]
|
|
91
|
-
after: [build_ios, build_android]
|
|
92
|
-
if: ${{ after.build_ios.status != 'failure' && after.build_android.status != 'failure' }}
|
|
93
|
-
type: require-approval
|
|
94
|
-
|
|
95
96
|
submit_ios:
|
|
96
97
|
name: Submit iOS to TestFlight
|
|
97
|
-
needs: [build_ios
|
|
98
|
+
needs: [build_ios]
|
|
98
99
|
if: ${{ needs.build_ios.outputs.build_id }}
|
|
99
100
|
type: submit
|
|
100
101
|
environment: production
|
|
@@ -104,7 +105,7 @@ jobs:
|
|
|
104
105
|
|
|
105
106
|
submit_android:
|
|
106
107
|
name: Submit Android to the internal track (draft)
|
|
107
|
-
needs: [build_android
|
|
108
|
+
needs: [build_android]
|
|
108
109
|
if: ${{ needs.build_android.outputs.build_id }}
|
|
109
110
|
type: submit
|
|
110
111
|
environment: production
|
|
@@ -113,8 +114,8 @@ jobs:
|
|
|
113
114
|
profile: production
|
|
114
115
|
|
|
115
116
|
update_ios:
|
|
116
|
-
name: Update iOS (
|
|
117
|
-
needs: [get_ios_build
|
|
117
|
+
name: Update iOS (every production install)
|
|
118
|
+
needs: [get_ios_build]
|
|
118
119
|
if: ${{ needs.get_ios_build.outputs.build_id }}
|
|
119
120
|
type: update
|
|
120
121
|
environment: production
|
|
@@ -124,15 +125,16 @@ jobs:
|
|
|
124
125
|
params:
|
|
125
126
|
channel: production
|
|
126
127
|
platform: ios
|
|
127
|
-
rollout_percentage:
|
|
128
|
+
# No rollout_percentage: unset, the update goes to every install. Set to 100, EAS published
|
|
129
|
+
# it as a rollout and a consumer app's update job failed ("GraphQL request failed").
|
|
128
130
|
# Explicit: unset, EAS tries a Sentry source map upload whenever @sentry/react-native is
|
|
129
131
|
# installed and only logs a failure. Set true once the Sentry plugin is on in app.config.ts
|
|
130
132
|
# (with SENTRY_AUTH_TOKEN), so a failed upload fails the job.
|
|
131
133
|
upload_sentry_sourcemaps: false
|
|
132
134
|
|
|
133
135
|
update_android:
|
|
134
|
-
name: Update Android (
|
|
135
|
-
needs: [get_android_build
|
|
136
|
+
name: Update Android (every production install)
|
|
137
|
+
needs: [get_android_build]
|
|
136
138
|
if: ${{ needs.get_android_build.outputs.build_id }}
|
|
137
139
|
type: update
|
|
138
140
|
environment: production
|
|
@@ -142,7 +144,8 @@ jobs:
|
|
|
142
144
|
params:
|
|
143
145
|
channel: production
|
|
144
146
|
platform: android
|
|
145
|
-
rollout_percentage:
|
|
147
|
+
# No rollout_percentage: unset, the update goes to every install. Set to 100, EAS published
|
|
148
|
+
# it as a rollout and a consumer app's update job failed ("GraphQL request failed").
|
|
146
149
|
# Explicit: unset, EAS tries a Sentry source map upload whenever @sentry/react-native is
|
|
147
150
|
# installed and only logs a failure. Set true once the Sentry plugin is on in app.config.ts
|
|
148
151
|
# (with SENTRY_AUTH_TOKEN), so a failed upload fails the job.
|
|
@@ -1,4 +1,5 @@
|
|
|
1
|
-
# Promote or roll back a staged production update
|
|
1
|
+
# Promote or roll back a staged production update: one published by hand with `--rollout-percentage`
|
|
2
|
+
# (deploy-production.yml sends every merge's update to every install).
|
|
2
3
|
#
|
|
3
4
|
# Run it by hand, from git:
|
|
4
5
|
#
|
|
@@ -40,7 +41,7 @@ on:
|
|
|
40
41
|
update_group_id:
|
|
41
42
|
type: string
|
|
42
43
|
required: true
|
|
43
|
-
description: One platform's update group
|
|
44
|
+
description: One platform's update group you published by hand with `--rollout-percentage` (`eas update:list --branch production`). deploy-production.yml publishes at 100%, which has no rollout to promote or roll back.
|
|
44
45
|
action:
|
|
45
46
|
type: choice
|
|
46
47
|
required: true
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@marktiderman/genesis-cli",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.23.0",
|
|
4
4
|
"private": false,
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "Genesis CLI — `genesis init` scaffolds a Genesis app (`--template native`: a new Expo app from the RN starter); `genesis add <block>` adds a block from what its package declares; `genesis migrate` copies new package migrations in and never rewrites an applied one; `genesis upgrade` moves every Genesis package to one release and refreshes the files Genesis owns; `genesis doctor` checks an app against the installed Genesis; `genesis studio init` turns the Data Studio on; `genesis introspect` writes a checked-in contract; `genesis features build|check` keeps generated feature docs in step with features.ts; `withGenesis()` (`app.plugin.js`, `/expo`) is the Expo config plugin; `/eslint` is Genesis's lint rules for an app's eslint.config.",
|