4 Commits

Include renames

Author	SHA1	Message	Date
pyh	1a9165fa4f	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
pyh	dbf6138df2	release: 1.0.1 ... Ships the rewritten README inside the package and pins the documented install specs to this version.	2026-09-30 11:54:43 +08:00
pyh	37468d6ac9	feat!: publish as @dsh-plugin/session-delete with an automated Gitea npm release ... The registry owner is the scope the package must publish under, so the name moves from @local/ to @dsh-plugin/ in all three places that must agree: package.json, cordis.patch.yml, and the client module id. `private` goes away because npm refuses to publish such a package, and publishConfig pins the registry to this organization's npm endpoint. The tag workflow publishes whatever version the pushed v* tag names, using the built-in Gitea job token, and refuses a tag that disagrees with package.json.	2026-09-30 11:00:39 +08:00
pyh	39a39adfec	feat: permanently delete a conversation, sweep orphaned spill files	2026-09-30 10:43:38 +08:00