laminate-cli 0.1.4__tar.gz → 0.1.5__tar.gz

{laminate_cli-0.1.4 → laminate_cli-0.1.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: laminate-cli
-Version: 0.1.4
+Version: 0.1.5
 Summary: Generate release-ready changelogs from git history using a local LLM
 Author-email: Apleut <me@apleut.dev>
 License-Expression: MIT
@@ -109,7 +109,7 @@ Laminate runs a **local GGUF model** using [`llama-cpp-python`](https://github.c
 
 Laminate looks for exactly one `.gguf` file in two places, in this order:
 
-1. **A `models/` folder in your current directory**, which the recommended location if you're running Laminate from a cloned repo:
+1. **A `models/` folder in your current directory**, which is the recommended location if you're running Laminate from a cloned repo:
 
    ```text
    models/
@@ -138,11 +138,7 @@ From inside a Git repository:
 laminate
 ```
 
-Laminate will read the repository's commit history, categorize the changes, and write the result to:
-
-```text
-CHANGELOG.md
-```
+Laminate will read the repository's commit history, categorize the changes, and write the result to `CHANGELOG.md`
 
 For example:
 
@@ -192,6 +188,9 @@ Process a specific Git commit range.
 laminate --range v1.0.0..v1.1.0
 ```
 
+> [!IMPORTANT]
+> Laminate does not currently support range formats like `v1.0.0..HEAD`. Version-to-present functionality will be added in a future release.
+
 `--range` overrides `--since` and `--until`.
 
 This is particularly useful when generating a changelog for a release.
@@ -319,7 +318,3 @@ If you find a problem with Laminate, please open an issue with:
 Or email me at [me@apleut.dev](me@apleut.dev).
 
 For changes to Laminate itself, pull requests are welcome.
-
-## License
-
-License information will be added before the first stable release.

{laminate_cli-0.1.4 → laminate_cli-0.1.5}/README.md

@@ -84,7 +84,7 @@ Laminate runs a **local GGUF model** using [`llama-cpp-python`](https://github.c
 
 Laminate looks for exactly one `.gguf` file in two places, in this order:
 
-1. **A `models/` folder in your current directory**, which the recommended location if you're running Laminate from a cloned repo:
+1. **A `models/` folder in your current directory**, which is the recommended location if you're running Laminate from a cloned repo:
 
    ```text
    models/
@@ -113,11 +113,7 @@ From inside a Git repository:
 laminate
 ```
 
-Laminate will read the repository's commit history, categorize the changes, and write the result to:
-
-```text
-CHANGELOG.md
-```
+Laminate will read the repository's commit history, categorize the changes, and write the result to `CHANGELOG.md`
 
 For example:
 
@@ -167,6 +163,9 @@ Process a specific Git commit range.
 laminate --range v1.0.0..v1.1.0
 ```
 
+> [!IMPORTANT]
+> Laminate does not currently support range formats like `v1.0.0..HEAD`. Version-to-present functionality will be added in a future release.
+
 `--range` overrides `--since` and `--until`.
 
 This is particularly useful when generating a changelog for a release.
@@ -293,8 +292,4 @@ If you find a problem with Laminate, please open an issue with:
 
 Or email me at [me@apleut.dev](me@apleut.dev).
 
-For changes to Laminate itself, pull requests are welcome.
-
-## License
-
-License information will be added before the first stable release.
+For changes to Laminate itself, pull requests are welcome.

{laminate_cli-0.1.4 → laminate_cli-0.1.5}/laminate_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: laminate-cli
-Version: 0.1.4
+Version: 0.1.5
 Summary: Generate release-ready changelogs from git history using a local LLM
 Author-email: Apleut <me@apleut.dev>
 License-Expression: MIT
@@ -109,7 +109,7 @@ Laminate runs a **local GGUF model** using [`llama-cpp-python`](https://github.c
 
 Laminate looks for exactly one `.gguf` file in two places, in this order:
 
-1. **A `models/` folder in your current directory**, which the recommended location if you're running Laminate from a cloned repo:
+1. **A `models/` folder in your current directory**, which is the recommended location if you're running Laminate from a cloned repo:
 
    ```text
    models/
@@ -138,11 +138,7 @@ From inside a Git repository:
 laminate
 ```
 
-Laminate will read the repository's commit history, categorize the changes, and write the result to:
-
-```text
-CHANGELOG.md
-```
+Laminate will read the repository's commit history, categorize the changes, and write the result to `CHANGELOG.md`
 
 For example:
 
@@ -192,6 +188,9 @@ Process a specific Git commit range.
 laminate --range v1.0.0..v1.1.0
 ```
 
+> [!IMPORTANT]
+> Laminate does not currently support range formats like `v1.0.0..HEAD`. Version-to-present functionality will be added in a future release.
+
 `--range` overrides `--since` and `--until`.
 
 This is particularly useful when generating a changelog for a release.
@@ -319,7 +318,3 @@ If you find a problem with Laminate, please open an issue with:
 Or email me at [me@apleut.dev](me@apleut.dev).
 
 For changes to Laminate itself, pull requests are welcome.
-
-## License
-
-License information will be added before the first stable release.

{laminate_cli-0.1.4 → laminate_cli-0.1.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "laminate-cli"
-version = "0.1.4"
+version = "0.1.5"
 authors = [
   { name="Apleut", email="me@apleut.dev" },
 ]