@indigoai/mcp-companion 0.1.0 → 0.1.2
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 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -46,4 +46,5 @@ npm run build
|
|
|
46
46
|
|
|
47
47
|
1. Push a tag `vX.Y.Z`. The pipeline writes that version into the package and the bundle.
|
|
48
48
|
2. Start the `mcpb` and `npm` jobs by hand in the tag's pipeline. Each runs once for production and once for staging.
|
|
49
|
-
3. The `mcpb` job fails unless the `MCPB_SIGNING_CERT` and `MCPB_SIGNING_KEY` file variables are set (plus `MCPB_SIGNING_INTERMEDIATE` when the chain needs one).
|
|
49
|
+
3. The `mcpb` job fails unless the `MCPB_SIGNING_CERT` and `MCPB_SIGNING_KEY` file variables are set (plus `MCPB_SIGNING_INTERMEDIATE` when the chain needs one). Protect the `v*` tags and mark these variables protected: protected variables only reach pipelines on protected tags, and an unprotected signing key is readable from any branch's pipeline.
|
|
50
|
+
4. The `npm` job publishes through npm trusted publishing, so GitLab holds no npm token. On npmjs.com, each of the two packages (Settings → Trusted publishing → GitLab CI/CD) trusts namespace `indigo.ai/product-engineers/product-team-leaders`, project `indigo-mcp-companion`, CI file `.gitlab-ci.yml`, with no environment. It works only on GitLab.com shared runners. Under Publishing access, both packages require two-factor authentication and disallow tokens. Packages are published without npm provenance, which needs a public source repository.
|