agentic-pi 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.
Files changed (2) hide show
  1. package/README.md +37 -0
  2. package/package.json +20 -1
package/README.md CHANGED
@@ -376,6 +376,43 @@ which walks `test/` for `*.test.ts`.
376
376
  Unit tests run in ~170 ms. Integration tests cost about $0.001 per run on
377
377
  `gpt-5.4-nano`.
378
378
 
379
+ ## Releasing
380
+
381
+ agentic-pi publishes to npm via a GitHub Actions workflow using **npm
382
+ trusted publishing** (OIDC) — no `NPM_TOKEN` secret is needed in the
383
+ repo.
384
+
385
+ To cut a release:
386
+
387
+ 1. Bump `version` in `package.json` (e.g. `0.1.0` → `0.2.0`).
388
+ 2. Commit the bump.
389
+ 3. Tag: `git tag v0.2.0 && git push --tags`.
390
+ 4. The `publish.yml` workflow runs: it verifies the tag matches
391
+ `package.json`, type-checks, builds, runs unit tests, then runs
392
+ `npm publish --provenance --access public`.
393
+
394
+ The workflow fails the publish step if the tag and `package.json` version
395
+ don't match — there is no path that publishes a version not represented
396
+ in the repo at that exact commit.
397
+
398
+ ### One-time setup (trusted publisher)
399
+
400
+ The first publish of a package needs to be done manually; subsequent
401
+ ones go through the workflow. To enable OIDC for this repo's publishes:
402
+
403
+ 1. Visit the package's "Trusted Publishers" page on
404
+ <https://www.npmjs.com/package/agentic-pi/settings>.
405
+ 2. Add a GitHub Actions trusted publisher with:
406
+ - Organization: `cliftonc`
407
+ - Repository: `agentic-pi`
408
+ - Workflow filename: `publish.yml`
409
+ - Environment: leave empty (the workflow doesn't use one)
410
+
411
+ After that, every tag push triggers a workflow that mints an OIDC token,
412
+ npm verifies it against the configured publisher, and the publish goes
413
+ through with a [provenance statement](https://docs.npmjs.com/generating-provenance-statements)
414
+ attached.
415
+
379
416
  Project layout:
380
417
 
381
418
  ```
package/package.json CHANGED
@@ -1,8 +1,27 @@
1
1
  {
2
2
  "name": "agentic-pi",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "A drop-in coding-agent harness built on earendil-works/pi, designed to replace opencode in workflow-driven systems like lastlight.",
5
5
  "license": "MIT",
6
+ "repository": {
7
+ "type": "git",
8
+ "url": "git+https://github.com/cliftonc/agentic-pi.git"
9
+ },
10
+ "homepage": "https://github.com/cliftonc/agentic-pi#readme",
11
+ "bugs": {
12
+ "url": "https://github.com/cliftonc/agentic-pi/issues"
13
+ },
14
+ "keywords": [
15
+ "agent",
16
+ "ai",
17
+ "coding-agent",
18
+ "pi",
19
+ "earendil-works",
20
+ "opencode",
21
+ "lastlight",
22
+ "llm",
23
+ "workflow"
24
+ ],
6
25
  "type": "module",
7
26
  "bin": {
8
27
  "agentic-pi": "./dist/cli.js"