@drawbridge/drawbridge-agents 0.1.92 → 0.1.93
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.
|
@@ -19,6 +19,15 @@ publisher as "GitHub Actions" (first proven with stripe 0.1.56, run 39975659406)
|
|
|
19
19
|
trusted publisher for each package is configured on npmjs.com by Darren. A developer pushes
|
|
20
20
|
the tag; an agent never does.
|
|
21
21
|
|
|
22
|
+
**drawbridge-agents publishes on merge (since 2026-10-23).** Merging a version bump to its
|
|
23
|
+
`main` publishes it and tags `v<version>`; a merge that keeps the version publishes nothing.
|
|
24
|
+
The session that merged then waits for `npm view @drawbridge/drawbridge-agents version` to
|
|
25
|
+
show it and runs `npx drawbridge-agents-bump @drawbridge/drawbridge-agents <version>`, leaving
|
|
26
|
+
out growth and any repo checked out on another release's branch (docs often is: bump docs on
|
|
27
|
+
`main` in a worktree). No GitHub key is involved (Darren, 2026-10-23: merging to main should
|
|
28
|
+
"publish agents and trigger the pin bump"). Merging is publishing, so whoever merges to agents
|
|
29
|
+
`main` decides. The other packages still publish on the tag push above.
|
|
30
|
+
|
|
22
31
|
The hand path below still works as a fallback when the workflow fails.
|
|
23
32
|
|
|
24
33
|
## Build + publish script
|
package/package.json
CHANGED