semversioner 3.0.0__tar.gz → 3.0.2__tar.gz

{semversioner-3.0.0/semversioner.egg-info → semversioner-3.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: semversioner
-Version: 3.0.0
+Version: 3.0.2
 Summary: Manage properly semver in your repository
 Author-email: Raul Gomis <raulgomis@gmail.com>
 License: MIT License
@@ -54,9 +54,11 @@ Dynamic: license-file
 
 # Semversioner
 
-The easiest way to manage [semantic versioning](https://semver.org/) in your project and generate `CHANGELOG.md` files automatically.
+**Release automation for AI-native software delivery.**
 
-Semversioner provides the tooling to automate the semver release process for libraries, docker images, microservices, and more.
+Semversioner makes it easy for developers and AI coding agents to manage
+[semantic versioning](https://semver.org/), capture changes, and generate `CHANGELOG.md` files automatically.
+It provides the tooling to automate releases for libraries, Docker images, microservices, and more.
 
 This project was inspired by the way AWS manages their versioning for [AWS-cli](https://github.com/aws/aws-cli/).
 
@@ -90,7 +92,7 @@ At any given time, the `.semversioner/` directory looks like:
 └── 1.1.2.json
 ```
 
-The release process takes everything in the `next-release` directory and aggregates them all together in a single JSON file for that release (e.g., `1.12.0.json`). This JSON file is a list of all the individual JSON files from `next-release`.
+The release process takes everything in the `next-release` directory and aggregates them all together in a single JSON file for that release (e.g., `1.12.0.json`). This JSON file is a list of all the individual JSON files from `next-release`, keeping release intent explicit and reviewable whether changes are authored by people or AI agents.
 
 ## Install
 

{semversioner-3.0.0 → semversioner-3.0.2}/README.md

@@ -1,8 +1,10 @@
 # Semversioner
 
-The easiest way to manage [semantic versioning](https://semver.org/) in your project and generate `CHANGELOG.md` files automatically.
+**Release automation for AI-native software delivery.**
 
-Semversioner provides the tooling to automate the semver release process for libraries, docker images, microservices, and more.
+Semversioner makes it easy for developers and AI coding agents to manage
+[semantic versioning](https://semver.org/), capture changes, and generate `CHANGELOG.md` files automatically.
+It provides the tooling to automate releases for libraries, Docker images, microservices, and more.
 
 This project was inspired by the way AWS manages their versioning for [AWS-cli](https://github.com/aws/aws-cli/).
 
@@ -36,7 +38,7 @@ At any given time, the `.semversioner/` directory looks like:
 └── 1.1.2.json
 ```
 
-The release process takes everything in the `next-release` directory and aggregates them all together in a single JSON file for that release (e.g., `1.12.0.json`). This JSON file is a list of all the individual JSON files from `next-release`.
+The release process takes everything in the `next-release` directory and aggregates them all together in a single JSON file for that release (e.g., `1.12.0.json`). This JSON file is a list of all the individual JSON files from `next-release`, keeping release intent explicit and reviewable whether changes are authored by people or AI agents.
 
 ## Install
 
@@ -195,4 +197,4 @@ Copyright (c) 2026 Raul Gomis.
 MIT licensed, see [LICENSE](LICENSE) file.
 
 ---
-Made with ♥ by [Raul Gomis](https://twitter.com/rgomis).
+Made with ♥ by [Raul Gomis](https://twitter.com/rgomis).

semversioner-3.0.2/semversioner/__version__.py

@@ -0,0 +1 @@
+__version__ = "3.0.2"

{semversioner-3.0.0 → semversioner-3.0.2}/semversioner/storage.py

@@ -159,6 +159,9 @@ class SemversionerFileSystemStorage(SemversionerStorage):
             Absolute path of the file generated.
         """
 
+        if not self.next_release_path.is_dir():
+            self.next_release_path.mkdir(parents=True)
+
         # Retry loop with atomic file creation to prevent race conditions
         while True:
             filename = f"{change.type}-{datetime.now(timezone.utc):%Y%m%d%H%M%S%f}.json"

{semversioner-3.0.0 → semversioner-3.0.2/semversioner.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: semversioner
-Version: 3.0.0
+Version: 3.0.2
 Summary: Manage properly semver in your repository
 Author-email: Raul Gomis <raulgomis@gmail.com>
 License: MIT License
@@ -54,9 +54,11 @@ Dynamic: license-file
 
 # Semversioner
 
-The easiest way to manage [semantic versioning](https://semver.org/) in your project and generate `CHANGELOG.md` files automatically.
+**Release automation for AI-native software delivery.**
 
-Semversioner provides the tooling to automate the semver release process for libraries, docker images, microservices, and more.
+Semversioner makes it easy for developers and AI coding agents to manage
+[semantic versioning](https://semver.org/), capture changes, and generate `CHANGELOG.md` files automatically.
+It provides the tooling to automate releases for libraries, Docker images, microservices, and more.
 
 This project was inspired by the way AWS manages their versioning for [AWS-cli](https://github.com/aws/aws-cli/).
 
@@ -90,7 +92,7 @@ At any given time, the `.semversioner/` directory looks like:
 └── 1.1.2.json
 ```
 
-The release process takes everything in the `next-release` directory and aggregates them all together in a single JSON file for that release (e.g., `1.12.0.json`). This JSON file is a list of all the individual JSON files from `next-release`.
+The release process takes everything in the `next-release` directory and aggregates them all together in a single JSON file for that release (e.g., `1.12.0.json`). This JSON file is a list of all the individual JSON files from `next-release`, keeping release intent explicit and reviewable whether changes are authored by people or AI agents.
 
 ## Install
 

semversioner-3.0.0/semversioner/__version__.py

@@ -1 +0,0 @@
-__version__ = "3.0.0"