@doidor/agentrig 0.5.3 → 0.6.0

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 +11 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -216,8 +216,17 @@ imported under `src/agent/`. Two backends ship today, selected by `AGENTRIG_PROV
216
216
 
217
217
  ## Releasing
218
218
 
219
- Publishing to npm is automated via GitHub Actions on each published GitHub Release — see
220
- [`RELEASING.md`](RELEASING.md) (requires an `NPM_TOKEN` repo secret).
219
+ Releases are automated by [Changesets](https://github.com/changesets/changesets) +
220
+ [`.github/workflows/release.yml`](.github/workflows/release.yml). The day-to-day flow:
221
+
222
+ 1. `npx changeset` → pick **patch/minor/major** + a one-line summary; commit it with your PR.
223
+ 2. Merge to `main` → the workflow opens a **"Version Packages"** PR that bumps the version and
224
+ updates `CHANGELOG.md`.
225
+ 3. Merge that PR → the workflow publishes `@doidor/agentrig` to npm **tokenlessly via OIDC**
226
+ (npm Trusted Publishing), with **automatic provenance**, and pushes the `vX.Y.Z` git tag.
227
+
228
+ No `NPM_TOKEN` secret, no manual `npm version`/`npm publish`. Setup (Trusted Publisher on
229
+ npmjs.com, Actions PR permission) is in [`RELEASING.md`](RELEASING.md).
221
230
 
222
231
  ## License
223
232
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@doidor/agentrig",
3
- "version": "0.5.3",
3
+ "version": "0.6.0",
4
4
  "description": "AgentRig — an agentic meta-harness. A CLI that investigates a repository and installs (and evaluates) a best-practice agent harness.",
5
5
  "type": "module",
6
6
  "bin": {