diff --git a/.autover/changes/8b6428ea-f0a2-45cd-af3e-d765bf0d69bb.json b/.autover/changes/8b6428ea-f0a2-45cd-af3e-d765bf0d69bb.json deleted file mode 100644 index 8f89b6b..0000000 --- a/.autover/changes/8b6428ea-f0a2-45cd-af3e-d765bf0d69bb.json +++ /dev/null @@ -1,16 +0,0 @@ -{ - "Projects": [ - { - "Name": "AutoVer", - "Type": "Minor", - "ChangelogMessages": [ - "Version Python projects: a pyproject.toml listed in autover.json is versioned through its [project] version (PEP 621), rewriting only that value so quoting, spacing, comments and line endings are kept as they were. A project without a version is seeded after its name, like the other project types", - "A pyproject.toml is never auto-discovered, because many repositories keep one purely for tool settings; discovering those would start versioning a lint config in repositories that rely on discovery today", - "Refused with an explanation rather than guessed at: a version listed in [project] dynamic (computed by the build backend), a [tool.poetry]-only project, a non-string version, and a version AutoVer cannot increment (a normalized spelling such as 1.2.3b1)", - "A prerelease label must be a Python pre-release (PEP 440): alpha, beta, rc (and their short forms), pre/preview or dev, optionally numbered. Anything else fails the release before any project file is written, rather than producing a package pip refuses to install (hotfix) or a post-release that pip installs ahead of the real version (post.1)", - "A version a pyproject.toml cannot take (not a valid Python version) now fails the release before any project file is written, so a repository mixing .csproj, Dockerfile and pyproject.toml projects is not left with the others bumped and staged", - "A project file that fails to load now reports why: the configuration-loading error includes the underlying cause (e.g. a missing project file, a pyproject.toml that cannot be versioned, or the JSON path of an invalid setting) instead of only naming autover.json" - ] - } - ] -} diff --git a/CHANGELOG.md b/CHANGELOG.md index c0fbe32..ba9e1b5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,13 @@ +## Release 2026-10-01 + +### AutoVer (1.5.0) +* Version Python projects: a pyproject.toml listed in autover.json is versioned through its [project] version (PEP 621), rewriting only that value so quoting, spacing, comments and line endings are kept as they were. A project without a version is seeded after its name, like the other project types +* A pyproject.toml is never auto-discovered, because many repositories keep one purely for tool settings; discovering those would start versioning a lint config in repositories that rely on discovery today +* Refused with an explanation rather than guessed at: a version listed in [project] dynamic (computed by the build backend), a [tool.poetry]-only project, a non-string version, and a version AutoVer cannot increment (a normalized spelling such as 1.2.3b1) +* A prerelease label must be a Python pre-release (PEP 440): alpha, beta, rc (and their short forms), pre/preview or dev, optionally numbered. Anything else fails the release before any project file is written, rather than producing a package pip refuses to install (hotfix) or a post-release that pip installs ahead of the real version (post.1) +* A version a pyproject.toml cannot take (not a valid Python version) now fails the release before any project file is written, so a repository mixing .csproj, Dockerfile and pyproject.toml projects is not left with the others bumped and staged +* A project file that fails to load now reports why: the configuration-loading error includes the underlying cause (e.g. a missing project file, a pyproject.toml that cannot be versioned, or the JSON path of an invalid setting) instead of only naming autover.json + ## Release 2026-09-16 ### AutoVer (1.4.0) diff --git a/src/AutoVer/AutoVer.csproj b/src/AutoVer/AutoVer.csproj index cdcdc8c..42d8101 100644 --- a/src/AutoVer/AutoVer.csproj +++ b/src/AutoVer/AutoVer.csproj @@ -18,7 +18,7 @@ README.md LICENSE icon.png - 1.4.0 + 1.5.0