json5-manifest-sync 0.3.5 → 0.3.6

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to this project are documented in this file.
 
+## [0.3.6] - 2026-11-09
+
+### Changed
+
+- Reframed the README introduction around the documented companion-manifest use case.
+
 ## [0.3.5] - 2026-11-09
 
 ### Changed

package/README.md

@@ -1,8 +1,8 @@
 # json5-manifest-sync
 
-Document your npm package manifest with comments in a companion `package.json5`, then sync it with the standard `package.json` expected by npm and other tools. Choose either file as the source of truth for manifest values; `package.json` always remains valid strict JSON.
+Add comments to your package manifest in a companion `package.json5`, then sync it with the standard `package.json` expected by npm and other tools. This works whether you use pnpm, which supports `package.json5` natively, or simply want a documented manifest while retaining compatibility with tools that require `package.json`. Choose either file as the source of truth for manifest values; `package.json` remains valid strict JSON.
 
-For example, document dependencies in `package.json5` and generate `package.json` from it:
+For example, document dependencies in `package.json5` and generate `package.json` for npm or other tools that require it:
 
 <!-- prettier-ignore -->
 ```json5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "json5-manifest-sync",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "description": "Sync package.json and package.json5 manifests in either direction, preserving JSON5 comments where possible.",
   "author": {
     "name": "Bradley Baysinger",