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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: laminate-cli
-Version: 0.1.4
+Version: 0.1.6
 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:
 
@@ -184,6 +180,9 @@ Only include commits before a specific date.
 laminate --until 2026-10-01
 ```
 
+> [!IMPORTANT]
+> Both `--since` and `--until` use YYYY-MM-DD format for dates.
+
 ### `--range`
 
 Process a specific Git commit range.
@@ -192,6 +191,12 @@ Process a specific Git commit range.
 laminate --range v1.0.0..v1.1.0
 ```
 
+You can also use `--range` to read commits from a specific version to the last commit, like this:
+
+```bash
+laminate --range v1.0.0..HEAD
+```
+
 `--range` overrides `--since` and `--until`.
 
 This is particularly useful when generating a changelog for a release.
@@ -240,6 +245,10 @@ Without `--release`, Laminate generates:
 ## [Unreleased]
 ```
 
+### `--append`
+
+Append the new changelog contents to the output file instead of completely overwriting them. Without `--append`, the changelog will only contain the commit range you specified. If you include `--append` though, it will simply add that release to the top of the file.
+
 ## Example
 
 Suppose your repository contains commits like:
@@ -319,7 +328,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.6}/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:
 
@@ -159,6 +155,9 @@ Only include commits before a specific date.
 laminate --until 2026-10-01
 ```
 
+> [!IMPORTANT]
+> Both `--since` and `--until` use YYYY-MM-DD format for dates.
+
 ### `--range`
 
 Process a specific Git commit range.
@@ -167,6 +166,12 @@ Process a specific Git commit range.
 laminate --range v1.0.0..v1.1.0
 ```
 
+You can also use `--range` to read commits from a specific version to the last commit, like this:
+
+```bash
+laminate --range v1.0.0..HEAD
+```
+
 `--range` overrides `--since` and `--until`.
 
 This is particularly useful when generating a changelog for a release.
@@ -215,6 +220,10 @@ Without `--release`, Laminate generates:
 ## [Unreleased]
 ```
 
+### `--append`
+
+Append the new changelog contents to the output file instead of completely overwriting them. Without `--append`, the changelog will only contain the commit range you specified. If you include `--append` though, it will simply add that release to the top of the file.
+
 ## Example
 
 Suppose your repository contains commits like:
@@ -293,8 +302,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.6}/laminate/cli.py

@@ -38,6 +38,7 @@ def generate(
     output: str = typer.Option("CHANGELOG.md", help="Path to write the generated changelog to."),
     batch_size: int = typer.Option(15, "--batch-size", help="Number of commits sent to the LLM per batch."),
     release: str = typer.Option(None, "--release", help="Version number for this release, e.g. 1.1.0. If omitted, the changelog is headed [Unreleased]."),
+    append: bool = typer.Option(False, "--append", help="Appends the new changelog contents to the existing file instead of overwriting it."),
     version: bool = typer.Option(
         False,
         "--version",
@@ -100,7 +101,7 @@ def generate(
         raise typer.Exit(code=1)
 
     changelog = render_changelog(entries, version=release)
-    write_changelog(changelog, output)
+    write_changelog(changelog, output, append)
 
     typer.echo(f"\nDone. Changelog written to {output}", file=sys.stdout)
 

{laminate_cli-0.1.4 → laminate_cli-0.1.6}/laminate/render.py

@@ -47,7 +47,14 @@ def render_changelog(entries: list[CategorizedEntry], version: str | None = None
     return "\n".join(lines).rstrip() + "\n"
 
 
-def write_changelog(content: str, output_path: str = "CHANGELOG.md") -> None:
+def write_changelog(content: str, output_path: str = "CHANGELOG.md", append: bool | None = None) -> None:
+    if append is True:
+        with open(output_path, "r", encoding="utf-8") as f:
+            existing_content = f.read()
+        existing_stub = existing_content[existing_content.find('## [') + 1:]
+
+    content = content + "\n" + existing_stub
+
     with open(output_path, "w", encoding="utf-8") as f:
         f.write(content)
 
@@ -67,5 +74,5 @@ if __name__ == "__main__":
         changelog = render_changelog(entries)
 
         print(changelog)
-        write_changelog(changelog)
+        write_changelog(changelog, append=True)
         print("Wrote changelog.md")

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: laminate-cli
-Version: 0.1.4
+Version: 0.1.6
 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:
 
@@ -184,6 +180,9 @@ Only include commits before a specific date.
 laminate --until 2026-10-01
 ```
 
+> [!IMPORTANT]
+> Both `--since` and `--until` use YYYY-MM-DD format for dates.
+
 ### `--range`
 
 Process a specific Git commit range.
@@ -192,6 +191,12 @@ Process a specific Git commit range.
 laminate --range v1.0.0..v1.1.0
 ```
 
+You can also use `--range` to read commits from a specific version to the last commit, like this:
+
+```bash
+laminate --range v1.0.0..HEAD
+```
+
 `--range` overrides `--since` and `--until`.
 
 This is particularly useful when generating a changelog for a release.
@@ -240,6 +245,10 @@ Without `--release`, Laminate generates:
 ## [Unreleased]
 ```
 
+### `--append`
+
+Append the new changelog contents to the output file instead of completely overwriting them. Without `--append`, the changelog will only contain the commit range you specified. If you include `--append` though, it will simply add that release to the top of the file.
+
 ## Example
 
 Suppose your repository contains commits like:
@@ -319,7 +328,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.6}/pyproject.toml

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