@matuto-ai/pi-broker-connector 0.1.0 → 0.1.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 +4 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -28,12 +28,12 @@ Or, after the npm-scope correction PR is merged into `main`:
|
|
|
28
28
|
pi install git:github.com/matuto-ai/pi-broker-connector
|
|
29
29
|
```
|
|
30
30
|
|
|
31
|
-
This uses the default branch; wait for the scope correction to merge first. To test before merge, append `@` and the exact reviewed commit from the scope-correction PR. Existing tags are unchanged and may still contain the old npm package identity; do not use an old tag as evidence of the new scope.
|
|
31
|
+
This uses the default branch; wait for the scope correction to merge first. To test before merge, append `@` and the exact reviewed commit from the scope-correction PR. Existing tags are unchanged and may still contain the old npm package identity; do not use an old tag as evidence of the new scope. Publish a new package version only after its source changes have been reviewed and the owner is ready to release it.
|
|
32
32
|
|
|
33
33
|
### From npm (only after publication)
|
|
34
34
|
|
|
35
35
|
```sh
|
|
36
|
-
pi install npm:@matuto-ai/pi-broker-connector@0.1.
|
|
36
|
+
pi install npm:@matuto-ai/pi-broker-connector@0.1.1
|
|
37
37
|
```
|
|
38
38
|
|
|
39
39
|
The proposed scope must be controlled by the publisher before publication. A repository name or workflow does not create an npm account/package. Until published, use the checkout route above; do not treat the npm command as currently available.
|
|
@@ -111,6 +111,8 @@ Tests cover private bundle validation, exact session isolation, duplicate owners
|
|
|
111
111
|
|
|
112
112
|
## Publishing
|
|
113
113
|
|
|
114
|
+
The `0.1.1` patch prepares the next trusted-publisher run without changing runtime behavior. After this version-bump PR is merged, the owner can create a GitHub release with tag **`v0.1.1`**. Preparing this PR does not publish that release or npm version.
|
|
115
|
+
|
|
114
116
|
The release workflow follows the existing Pi plugin convention: a published GitHub release triggers checks and npm publishing. It requires a `v<package.version>` tag and runs the native host gate before publishing. Nothing is published by CI on pull requests or ordinary pushes.
|
|
115
117
|
|
|
116
118
|
For OIDC trusted publishing, configure the npm package's trusted publisher for GitHub owner `matuto-ai`, repo `pi-broker-connector`, workflow **`npm-publish.yml`** (filename only), allowing direct `npm publish`. No `NPM_TOKEN` is embedded or created. Use npm CLI >=11.5.1 with the supported Node version. If the npm package does not yet exist, the owner must complete the first package publication/account setup using npm's supported process before configuring its package settings. That setup is not performed by this repository. If the first manual publication uses `0.1.0`, bump the package version and matching release tag before the next automated publish; npm does not allow republishing the same version.
|