@clubnet/seedclub 0.2.15 → 0.2.17

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 +34 -15
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -4,6 +4,16 @@ The Human+ Venture Network — AI agent for deal sourcing, research, and signal
4
4
 
5
5
  Requirements: Node.js 22+
6
6
 
7
+ ## Source of truth
8
+
9
+ This repo is the source of truth for the published Seed Club wrapper package:
10
+
11
+ - GitHub repo: `seedclub/seedclub-agent`
12
+ - npm package: `@clubnet/seedclub`
13
+ - user-facing command: `seedclub`
14
+
15
+ This is the Pi wrapper repo, not the older extracted full-agent monorepo.
16
+
7
17
  ## Install
8
18
 
9
19
  ```bash
@@ -126,10 +136,13 @@ Colors can be hex (`"#00C853"`), 256-color palette index (`242`), a reference to
126
136
  git clone https://github.com/seedclub/seedclub-agent.git
127
137
  cd seedclub-agent
128
138
 
129
- # Install locally from the repo
139
+ # Install deps, then install locally from the repo
140
+ npm install
130
141
  npm install -g ./
131
142
  ```
132
143
 
144
+ For day-to-day work, run `seedclub version` after installing to confirm your shell is using this repo's wrapper build.
145
+
133
146
  ### Repo structure
134
147
 
135
148
  ```
@@ -203,25 +216,31 @@ For reproducible extension dependency installs, commit `assets/extensions/seedcl
203
216
 
204
217
  ### Release process
205
218
 
206
- Standard order: **GitHub first, npm second**. Always publish from a tagged commit on `main`.
219
+ Publishing is now handled by npm trusted publishing from GitHub Actions.
220
+
221
+ Workflow:
207
222
 
208
- 1. Create a branch, make changes, open PR
223
+ 1. Create a branch and make changes
209
224
  2. Merge to `main`
210
- 3. Pull `main`, run `npm install -g ./` and smoke test (`seedclub`)
211
- 4. Bump version: `npm version patch|minor|major` (creates a git tag)
212
- 5. Push commits + tags: `git push --follow-tags`
213
- 6. Publish from that tag: `npm publish`
225
+ 3. Pull `main`, run `npm install`, then `npm install -g ./`
226
+ 4. Smoke test with `seedclub version` and, if relevant, a quick interactive run
227
+ 5. Bump version: `npm version patch|minor|major`
228
+ 6. Push commits + tags: `git push --follow-tags`
229
+ 7. GitHub Actions publishes the tagged release to npm automatically via `.github/workflows/publish.yml`
214
230
 
215
- ### Publishing
231
+ ### Trusted publishing
216
232
 
217
- ```bash
218
- # One-time setup
219
- echo "@clubnet:registry=https://registry.npmjs.org/" >> ~/.npmrc
220
- echo "//registry.npmjs.org/:_authToken=YOUR_NPM_TOKEN" >> ~/.npmrc
233
+ The npm package is configured to publish from GitHub Actions, not from long-lived local npm tokens.
221
234
 
222
- # Publish
223
- npm publish --access restricted
224
- ```
235
+ Trusted publisher settings for `@clubnet/seedclub`:
236
+
237
+ - Provider: GitHub Actions
238
+ - Organization or user: `seedclub`
239
+ - Repository: `seedclub-agent`
240
+ - Workflow filename: `publish.yml`
241
+ - Environment name: blank
242
+
243
+ Once trusted publishing is working, npm package publishing access should stay on the stricter setting that disallows token-based publishing.
225
244
 
226
245
  ## Update
227
246
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clubnet/seedclub",
3
- "version": "0.2.15",
3
+ "version": "0.2.17",
4
4
  "description": "The Human+ Venture Network — AI agent for deal sourcing, research, and signal tracking",
5
5
  "license": "MIT",
6
6
  "repository": {