puml-for-markdown 2.0.0 → 2.0.1

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,10 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.0.1
4
+
5
+ - Correct outdated README statements about Windows support, automated testing,
6
+ the pre-commit hook, and diagram privacy. No runtime behavior changes.
7
+
3
8
  ## 2.0.0
4
9
 
5
10
  ### Migration from version 1
package/README.md CHANGED
@@ -88,8 +88,8 @@ installing `latest` will select version 2 once it is published. See the
88
88
  ### Advanced Usage
89
89
  Here are some other features supported
90
90
  - You can specify the CLI to output the diagram images as png and/or svg see `--output-images` and `--image-formats`.
91
- For an example of outputted images, checkout [dist_puml/puml](./dist_puml/puml). These images were created by the
92
- [pre-commit hook](./.husky/pre-commit).
91
+ For historical examples of exported images, see [dist_puml/puml](./dist_puml/puml).
92
+ The current pre-commit hook runs the automated tests.
93
93
  - You can specify the PUML server used to render the diagrams see `--puml-server-url`
94
94
 
95
95
  ### All CLI Options
@@ -173,18 +173,26 @@ In order to support `!include` we parse puml files and replace any `!include` wi
173
173
  #### Parsing Markdown
174
174
  The markdown files are then parsed for markdown comments. If the comments reference a PlantUML file, a link to the web
175
175
  service url will be added next to the comment. Because these links contain the full PlantUML diagram encoding in it,
176
- there are no issues using them in private repositories.
176
+ the source can be recovered from the URL. A private repository does not make the
177
+ renderer or shortener private; see [diagram privacy](#reliability-and-operational-notes).
177
178
 
178
179
  ### Testing
179
- Currently there is no TDD, for now I've just been using the example diagrams to test. The examples are pretty extensive
180
- though.
180
+ Run `npm test` to execute the automated CLI regression tests. CI runs on Linux,
181
+ macOS, and Windows with Node.js 22 and 24. The suite covers Markdown updates,
182
+ path handling, ignore rules, includes, image exports, caching, and shortening.
183
+ See [CONTRIBUTING.md](https://github.com/danielyaa5/puml-for-markdown/blob/main/CONTRIBUTING.md)
184
+ for development instructions.
181
185
 
182
186
  ### Other Helpful Links
183
187
  * [C4-Puml](https://github.com/plantuml-stdlib/C4-PlantUML): A collection of PlantUML diagrams for use in C4, you'll see me using this in my examples
184
188
 
185
- ### Known Issues
186
- * Seems to be breaking on Windows, see [here](https://github.com/danielyaa5/puml-for-markdown/issues/6). I don't have a
187
- Windows machine to test on so help here would be appreciated.
189
+ ### Windows support
190
+ Version 2 fixes the reported Windows path lookup issue
191
+ ([#6](https://github.com/danielyaa5/puml-for-markdown/issues/6)). Windows path and
192
+ ignore-rule regressions are covered by automated tests. The version 2 changes
193
+ were also tested on Windows 11 ARM64 with Node.js 24.
194
+
195
+ For remaining limitations, see [reliability and operational notes](#reliability-and-operational-notes).
188
196
 
189
197
  ### More Examples
190
198
  [![ERD](https://tinyurl.com/2amb263t)](https://tinyurl.com/2amb263t)<!--![ERD](./puml/level_4_erd.puml)-->
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "puml-for-markdown",
3
- "version": "2.0.0",
3
+ "version": "2.0.1",
4
4
  "description": "An application to add interactive PUML diagrams to your github markdown files. If running with default arguments, run in project root directory.",
5
5
  "main": "index.js",
6
6
  "scripts": {