bb-plugin-manifest 0.17.0 → 0.17.1

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 CHANGED
@@ -27,15 +27,16 @@ once to sign in.
27
27
 
28
28
  ## Install
29
29
 
30
- For a release published to npm, install the prebuilt package on the computer
31
- running your bb server (an enrolled agent machine can be a different computer):
30
+ Install the prebuilt package through the CLI connected to your bb server. An
31
+ agent can run this command on an enrolled machine: the CLI asks the bb server
32
+ to download and install the package on the server's computer.
32
33
 
33
34
  ```sh
34
35
  bb plugin install npm:bb-plugin-manifest@latest
35
36
  ```
36
37
 
37
- This route does not need Git or Xcode Command Line Tools. Until the first npm
38
- release is published, use the existing Git source (which requires Git):
38
+ This route does not need Git or Xcode Command Line Tools. The first npm release
39
+ is 0.17.0. The existing Git source is also supported (and requires Git):
39
40
 
40
41
  ```sh
41
42
  bb plugin install https://github.com/dpetrakov/manifest-bb-plugins --plugin manifest
@@ -101,9 +102,21 @@ the reviewed archive:
101
102
  npm publish /absolute/path/to/release/bb-plugin-manifest-X.Y.Z.tgz --access public --registry=https://registry.npmjs.org/
102
103
  ```
103
104
 
104
- Complete any npm authentication prompt yourself. Verify the release with
105
- `npm view bb-plugin-manifest version dist.integrity`, then test a fresh npm
106
- install in a separate bb server. Users who installed with `@latest` update with
105
+ Complete any npm authentication prompt yourself. A successful `npm publish`
106
+ exit alone does not prove availability: the first release can temporarily show
107
+ only a `0.0.0-stage` placeholder. Check that the actual version is visible,
108
+ `latest` points to it, and `dist.integrity` matches the reviewed archive:
109
+
110
+ ```sh
111
+ npm view bb-plugin-manifest@X.Y.Z version dist.integrity
112
+ npm view bb-plugin-manifest dist-tags
113
+ ```
114
+
115
+ If a version is staged for maintainer approval, use the npm website or
116
+ `npm stage list` and `npm stage approve` (requires npm 11.15+ and 2FA). Do not
117
+ publish the same version again to work around a pending release. After checking
118
+ the registry, test a fresh npm install in a separate bb server.
119
+ Every subsequent release needs a new version. Users installed with `@latest` update with
107
120
  `bb plugin update manifest`. An existing Git installation keeps tracking Git;
108
121
  do not remove it just to switch sources, because removal deletes its settings.
109
122