@usepowerplant/cli 0.4.10 → 0.4.11
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 +8 -1
- package/dist/cli.js +3799 -2400
- package/dist/menubar/Powerplant.app.zip +0 -0
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -140,6 +140,9 @@ report the current choice, and `powerplant update --automatic on` or
|
|
|
140
140
|
release already out installs now rather than at the next hourly check. A
|
|
141
141
|
release that fails to install is not retried by itself; the menu bar shows
|
|
142
142
|
the failure with a retry and the update log, and the next release clears it.
|
|
143
|
+
The one exception is a registry that does not serve the release yet (npm's
|
|
144
|
+
cache can lag a publish by a few minutes): the sync tries that release
|
|
145
|
+
again on its next hourly checks, up to three times, and the menu says so.
|
|
143
146
|
|
|
144
147
|
Powerplant also publishes the oldest version it still supports. When yours
|
|
145
148
|
is older, `powerplant status`, `powerplant doctor`, the menu bar app, and
|
|
@@ -162,7 +165,11 @@ to test `next` while keeping your production install on its promoted version.
|
|
|
162
165
|
while the service is running. Sleeping machines, disabled updates, and
|
|
163
166
|
failed installs can leave a machine behind. Verify the installed staging
|
|
164
167
|
version and exercise sync and the menu actions you changed before
|
|
165
|
-
promoting; elapsed time alone is not evidence of testing.
|
|
168
|
+
promoting; elapsed time alone is not evidence of testing. Promote only
|
|
169
|
+
after the workflow's "Wait until npm serves the release" step is green:
|
|
170
|
+
npm's CDN caches the package document for about five minutes after a
|
|
171
|
+
publish, and a production machine that checks inside that window gets
|
|
172
|
+
"no matching version" and waits an hour to try again.
|
|
166
173
|
2. **Promote.** From a repo checkout with npm package access and `gh`
|
|
167
174
|
signed in, name the version you tested:
|
|
168
175
|
|