agentic-pi 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 +42 -0
- package/package.json +20 -1
package/README.md
CHANGED
|
@@ -376,6 +376,48 @@ 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 (recommended path):
|
|
386
|
+
|
|
387
|
+
1. Bump `version` in `package.json` — `npm version patch` does this, plus
|
|
388
|
+
commit and tag, in one step.
|
|
389
|
+
2. Push the commit and tag: `git push --follow-tags`.
|
|
390
|
+
3. Create a GitHub Release on the new tag, e.g.
|
|
391
|
+
`gh release create v0.2.0 --generate-notes` or via the GitHub web UI.
|
|
392
|
+
4. The `publish.yml` workflow runs on the `release: published` event.
|
|
393
|
+
|
|
394
|
+
The workflow also triggers on bare `v*.*.*` tag pushes and on manual
|
|
395
|
+
`workflow_dispatch`. The `release` event is the preferred path because
|
|
396
|
+
tag-push events get suppressed when a tag is pushed in the same `git
|
|
397
|
+
push` invocation as branch commits — a real GitHub Actions quirk.
|
|
398
|
+
|
|
399
|
+
The publish step fails if the tag (or the dispatch `ref` input) doesn't
|
|
400
|
+
match `package.json` version — there is no path that publishes a version
|
|
401
|
+
not represented in the repo at that exact commit.
|
|
402
|
+
|
|
403
|
+
### One-time setup (trusted publisher)
|
|
404
|
+
|
|
405
|
+
The first publish of a package needs to be done manually; subsequent
|
|
406
|
+
ones go through the workflow. To enable OIDC for this repo's publishes:
|
|
407
|
+
|
|
408
|
+
1. Visit the package's "Trusted Publishers" page on
|
|
409
|
+
<https://www.npmjs.com/package/agentic-pi/settings>.
|
|
410
|
+
2. Add a GitHub Actions trusted publisher with:
|
|
411
|
+
- Organization: `cliftonc`
|
|
412
|
+
- Repository: `agentic-pi`
|
|
413
|
+
- Workflow filename: `publish.yml`
|
|
414
|
+
- Environment: leave empty (the workflow doesn't use one)
|
|
415
|
+
|
|
416
|
+
After that, every tag push triggers a workflow that mints an OIDC token,
|
|
417
|
+
npm verifies it against the configured publisher, and the publish goes
|
|
418
|
+
through with a [provenance statement](https://docs.npmjs.com/generating-provenance-statements)
|
|
419
|
+
attached.
|
|
420
|
+
|
|
379
421
|
Project layout:
|
|
380
422
|
|
|
381
423
|
```
|
package/package.json
CHANGED
|
@@ -1,8 +1,27 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agentic-pi",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
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"
|