coordigent 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 +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,7 +45,7 @@ or gains an install-time script. Both that check and the release checks are
|
|
|
45
45
|
`.github/workflows/publish-npm.yml` publishes on a tag `npm-v<version>` (the `v*` tags publish the
|
|
46
46
|
container image and never touch npm), or by hand from Actions with an existing tag. It uses npm
|
|
47
47
|
trusted publishing: no `NPM_TOKEN`; npm trades the job's GitHub OIDC token for a one-time
|
|
48
|
-
credential, and `npm publish --
|
|
48
|
+
credential, and `npm publish --access public` publishes it (no provenance: npm only attests public source repos, and this repo is private). Before
|
|
49
49
|
publishing, `scripts/release-checks.js release <tag>` refuses, with the reason, when:
|
|
50
50
|
|
|
51
51
|
- the tag is not exactly `npm-v` plus `package.json`'s `version`;
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "coordigent",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Runs Coordigent's coord CLI: downloads the coord and coord-mcp binaries for this machine on first run, checks their SHA-256, and runs coord.",
|
|
5
5
|
"homepage": "https://coordigent.com",
|
|
6
6
|
"repository": {
|