release: 1.0.2, and learn whether the built-in job token can publish

The publish step now tries the built-in Gitea job token first, prints which user it belongs to, falls back to NPM_TOKEN when the registry rejects it, and reports which token actually published. A 409 keeps meaning 'already published', so a re-run stays harmless.
2026-09-30 14:29:02 +08:00
parent c842cd0118
commit 1a9165fa4f
3 changed files with 58 additions and 25 deletions
@@ -1,6 +1,6 @@
 {
  "name": "@dsh-plugin/session-delete",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "description": "Permanently delete a conversation: stop it, remove its session log, subagent logs, and spilled tool output, and drop every registry reference. Settings → General can sweep orphaned temporary files left by conversations that are gone.",
  "type": "module",
  "license": "MIT",