@cloro-dev/response-parser 0.5.2 → 0.5.3

package/README.md

@@ -238,6 +238,10 @@ The core parsing logic is identical - you just need to handle the HTML rendering
 
 ## What's Changed
 
+### v0.5.3
+
+- First release from the Publish workflow, with npm Trusted Publishing and provenance. No library changes
+
 ### v0.5.2
 
 - ✅ **Fixed** The README said that the parser sanitizes HTML. It removes only `<script>` and `<noscript>` elements. A new Security note tells you to sanitize untrusted HTML before you render it
@@ -342,33 +346,19 @@ pnpm lint
 
 ## Release
 
-1. Log in to npm with an account that can publish to `@cloro-dev`:
-
-   ```bash
-   npm login
-   ```
-
-2. Run the checks and the build:
+The [Publish workflow](.github/workflows/publish.yml) publishes the package to npm when a version tag is pushed. It uses npm Trusted Publishing, so you do not need to log in to npm.
 
-   ```bash
-   pnpm type-check && pnpm lint && pnpm build
-   ```
-
-3. Increase the version. This changes `package.json` and creates a git commit and tag:
-
-   ```bash
-   npm version patch   # 0.4.5 → 0.4.6
-   npm version minor   # 0.4.5 → 0.5.0
-   npm version major   # 0.4.5 → 1.0.0
-   ```
+1. Add an entry under "What's Changed".
 
-4. Publish. `prepublishOnly` builds the package again before the upload:
+2. Increase the version. This changes `package.json` and creates a git commit and a `v` tag:
 
    ```bash
-   npm publish
+   npm version patch   # 0.5.2 → 0.5.3
+   npm version minor   # 0.5.2 → 0.6.0
+   npm version major   # 0.5.2 → 1.0.0
    ```
 
-5. Push the commit and the tag, and add an entry under "What's Changed":
+3. Push the commit and the tag. The workflow type-checks, lints, builds and publishes:
 
    ```bash
    git push --follow-tags

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloro-dev/response-parser",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "type": "module",
   "description": "Parse and render AI model responses from ChatGPT, Gemini, Perplexity, and more",
   "main": "dist/index.cjs",