@dumbmice/pi-deepseek-websearch 0.1.1 → 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/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.2 — 2026-10-30
4
+
5
+ - README: document the release path in full — trusted publishing via GitHub OIDC, no
6
+ `NPM_TOKEN`, automatic provenance, the tag/version guard, and the option to disallow
7
+ token publishing once trusted publishing is proven.
8
+
3
9
  ## 0.1.1 — 2026-10-30
4
10
 
5
11
  Documentation-only release: npm snapshots the README at publish time, so this
package/README.md CHANGED
@@ -167,8 +167,11 @@ The suite covers query trimming order and the 128 cap, caller-spacing preservati
167
167
 
168
168
  ## Releasing
169
169
 
170
- Versions are published from CI with npm [trusted publishing](https://docs.npmjs.com/trusted-publishers)
171
- (OIDC, no long-lived token, provenance attached):
170
+ Versions are published from CI with npm [trusted publishing](https://docs.npmjs.com/trusted-publishers):
171
+ the workflow exchanges a GitHub OIDC token for a short-lived publish credential, so the repository
172
+ holds **no `NPM_TOKEN` secret** and no long-lived write credential (including a 2FA-bypass token)
173
+ is needed or permitted. Because the repository is public, npm attaches a **provenance attestation**
174
+ automatically — no `--provenance` flag.
172
175
 
173
176
  ```bash
174
177
  npm version patch --no-git-tag-version # or minor/major
@@ -177,6 +180,12 @@ git tag "v$(node -p "require('./package.json').version")"
177
180
  git push origin main --follow-tags # .github/workflows/publish.yml runs test + typecheck, then publishes
178
181
  ```
179
182
 
183
+ `.github/workflows/publish.yml` runs the 68 tests and the typecheck, and refuses to publish when the
184
+ pushed tag and `package.json` version disagree, so a mis-versioned tag fails the build instead of
185
+ shipping the wrong number. For maximum safety the package's *Publishing access* can then be set to
186
+ "Require two-factor authentication and disallow tokens": trusted publishing keeps working, token
187
+ publishing stops.
188
+
180
189
  ## License
181
190
 
182
191
  MIT. Issues and source: <https://github.com/DumbMice/pi-deepseek-websearch>.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dumbmice/pi-deepseek-websearch",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Web search and page fetch for pi via DeepSeek's Search & Fetch APIs: publication dates, authority, rerank score, ori_question, count up to 50, and graceful 128-char handling. Coexists with pi-web-access.",
5
5
  "type": "module",
6
6
  "license": "MIT",