chore: release v10.5.0

Automatically generated by python-semantic-release

Author: semantic-release

CHANGELOG.rst

@@ -4,6 +4,93 @@
 CHANGELOG
 =========
 
+.. _changelog-v10.5.0:
+
+v10.5.0 (2025-11-09)
+====================
+
+✨ Features
+-----------
+
+* **cmd-version**: Add automatic repository un-shallowing to version workflow (`PR#1366`_,
+  `90a1ffa`_)
+
+* **cmd-version**: Add functionality to create & update partial version tags (`PR#1115`_,
+  `a28f940`_)
+
+* **cmd-version**: Adds c-macro style version definition support to ``version_variables``, closes
+  `#1348`_ (`PR#1349`_, `4ce1fca`_)
+
+* **cmd-version**: Adds upstream check into workflow to prevent commit push collisions (`PR#1360`_,
+  `d77193e`_)
+
+🪲 Bug Fixes
+------------
+
+* **cmd-version**: Prevent regular expression errors on ``tag_format`` (`PR#1367`_, `e7d7aa7`_)
+
+📖 Documentation
+----------------
+
+* **commands**: Add description of automated upstream version checking upon version creation
+  (`PR#1360`_, `d77193e`_)
+
+* **configuration**: Add description for ``add_partial_tags`` setting & usage examples (`PR#1115`_,
+  `a28f940`_)
+
+* **configuration**: Fix ``tag_format`` definition (`PR#1367`_, `e7d7aa7`_)
+
+* **configuration**: Update ``version_variables`` examples with a c-macro style replacement
+  (`PR#1349`_, `4ce1fca`_)
+
+* **github-actions**: Adds release job outputs definition to example (`PR#1344`_, `0fb4875`_)
+
+* **github-actions**: Removed verify upstream status step from example workflow (`PR#1360`_,
+  `d77193e`_)
+
+* **github-actions**: Update example to remove need to specify repo checkout's fetch depth
+  (`PR#1366`_, `90a1ffa`_)
+
+* **uv-integration**: Remove verify upstream check from uv integration example (`PR#1360`_,
+  `d77193e`_)
+
+* **uv-integration**: Update example to remove need to specify repo checkout's fetch depth
+  (`PR#1366`_, `90a1ffa`_)
+
+⚙️ Build System
+----------------
+
+* **deps**: Bump ``tomlkit`` dependency from ~=0.11.0 to ~=0.13.0 (`PR#1355`_, `55c94ec`_)
+
+* **deps**: Change github-actions container image to ``python:3.14-slim-trixie`` (`PR#1346`_,
+  `1a23712`_)
+
+💡 Additional Release Information
+---------------------------------
+
+* **cmd-version**: If you were previously handling the unshallowing of a repository clone in your
+  CI/CD pipelines, you may now remove that step from your workflow. PSR will now detect a shallow
+  repository and unshallow it before evaluating the commit history.
+
+.. _#1348: https://github.com/python-semantic-release/python-semantic-release/issues/1348
+.. _0fb4875: https://github.com/python-semantic-release/python-semantic-release/commit/0fb4875fa24ed283ed2d97ff6ab1879669a787ca
+.. _1a23712: https://github.com/python-semantic-release/python-semantic-release/commit/1a237125badcb597ae7a92db4e01c2ff3293bce8
+.. _4ce1fca: https://github.com/python-semantic-release/python-semantic-release/commit/4ce1fcac60ac73657a4aaaaa3cb7c4afc7eac2c1
+.. _55c94ec: https://github.com/python-semantic-release/python-semantic-release/commit/55c94ecde1aec47b88aa172d031ab33afa7f795d
+.. _90a1ffa: https://github.com/python-semantic-release/python-semantic-release/commit/90a1ffa55c5a1605c59cb26a1797f9a37fdfa784
+.. _a28f940: https://github.com/python-semantic-release/python-semantic-release/commit/a28f9401c4b285aa1007b72eb051d42567f33f93
+.. _d77193e: https://github.com/python-semantic-release/python-semantic-release/commit/d77193e30807968ba6a26bd356a868db62dc1098
+.. _e7d7aa7: https://github.com/python-semantic-release/python-semantic-release/commit/e7d7aa74a216cd2fdd78afc1e0e8b6b8044954ec
+.. _PR#1115: https://github.com/python-semantic-release/python-semantic-release/pull/1115
+.. _PR#1344: https://github.com/python-semantic-release/python-semantic-release/pull/1344
+.. _PR#1346: https://github.com/python-semantic-release/python-semantic-release/pull/1346
+.. _PR#1349: https://github.com/python-semantic-release/python-semantic-release/pull/1349
+.. _PR#1355: https://github.com/python-semantic-release/python-semantic-release/pull/1355
+.. _PR#1360: https://github.com/python-semantic-release/python-semantic-release/pull/1360
+.. _PR#1366: https://github.com/python-semantic-release/python-semantic-release/pull/1366
+.. _PR#1367: https://github.com/python-semantic-release/python-semantic-release/pull/1367
+
+
 .. _changelog-v10.4.1:
 
 v10.4.1 (2025-09-13)

docs/configuration/automatic-releases/github-actions.rst

@@ -893,14 +893,14 @@ to the GitHub Release Assets as well.
           - name: Action | Semantic Version Release
             id: release
             # Adjust tag with desired version if applicable.
-            uses: python-semantic-release/python-semantic-release@v10.4.1
+            uses: python-semantic-release/python-semantic-release@v10.5.0
             with:
               github_token: ${{ secrets.GITHUB_TOKEN }}
               git_committer_name: "github-actions"
               git_committer_email: "actions@users.noreply.github.com"
 
           - name: Publish | Upload to GitHub Release Assets
-            uses: python-semantic-release/publish-action@v10.4.1
+            uses: python-semantic-release/publish-action@v10.5.0
             if: steps.release.outputs.released == 'true'
             with:
               github_token: ${{ secrets.GITHUB_TOKEN }}
@@ -969,15 +969,15 @@ to the GitHub Release Assets as well.
   the ``token`` input) in order to gain push access.
 
 .. note::
-  As of $NEW_RELEASE_TAG, Python Semantic Release automatically detects and converts
+  As of v10.5.0, Python Semantic Release automatically detects and converts
   shallow clones to full clones when needed. While you can still use ``fetch-depth: 0``
   with ``actions/checkout@v4`` to fetch the full history upfront, it is no longer
   required. If you use the default shallow clone, Python Semantic Release will
   automatically fetch the full history before evaluating commits. If you are using
   an older version of PSR, you will need to unshallow the repository prior to use.
 
 .. note::
-  As of $NEW_RELEASE_TAG, the verify upstream step is no longer required as it has been
+  As of v10.5.0, the verify upstream step is no longer required as it has been
   integrated into PSR directly. If you are using an older version of PSR, you will need
   to review the older documentation for that step. See Issue `#1201`_ for more details.
 
@@ -1005,7 +1005,7 @@ The equivalent GitHub Action configuration would be:
 
   - name: Action | Semantic Version Release
     # Adjust tag with desired version if applicable.
-    uses: python-semantic-release/python-semantic-release@v10.4.1
+    uses: python-semantic-release/python-semantic-release@v10.5.0
     with:
       github_token: ${{ secrets.GITHUB_TOKEN }}
       force: patch
@@ -1064,14 +1064,14 @@ Publish Action.
 
         - name: Release submodule 1
           id: release-submod-1
-          uses: python-semantic-release/python-semantic-release@v10.4.1
+          uses: python-semantic-release/python-semantic-release@v10.5.0
           with:
             directory: ${{ env.SUBMODULE_1_DIR }}
             github_token: ${{ secrets.GITHUB_TOKEN }}
 
         - name: Release submodule 2
           id: release-submod-2
-          uses: python-semantic-release/python-semantic-release@v10.4.1
+          uses: python-semantic-release/python-semantic-release@v10.5.0
           with:
             directory: ${{ env.SUBMODULE_2_DIR }}
             github_token: ${{ secrets.GITHUB_TOKEN }}
@@ -1083,15 +1083,15 @@ Publish Action.
         # ------------------------------------------------------------------- #
 
         - name: Publish | Upload package 1 to GitHub Release Assets
-          uses: python-semantic-release/publish-action@v10.4.1
+          uses: python-semantic-release/publish-action@v10.5.0
           if: steps.release-submod-1.outputs.released == 'true'
           with:
             directory: ${{ env.SUBMODULE_1_DIR }}
             github_token: ${{ secrets.GITHUB_TOKEN }}
             tag: ${{ steps.release-submod-1.outputs.tag }}
 
         - name: Publish | Upload package 2 to GitHub Release Assets
-          uses: python-semantic-release/publish-action@v10.4.1
+          uses: python-semantic-release/publish-action@v10.5.0
           if: steps.release-submod-2.outputs.released == 'true'
           with:
             directory: ${{ env.SUBMODULE_2_DIR }}

docs/configuration/configuration.rst

@@ -1398,7 +1398,7 @@ The regular expression generated from the ``version_variables`` definition will:
 2. The variable name defined by ``variable`` and the version must be separated by
    an operand symbol (``=``, ``:``, ``:=``, or ``@``). Whitespace is optional around
    the symbol. As of v10.0.0, a double-equals (``==``) operator is also supported
-   as a valid operand symbol. As of $NEW_RELEASE_TAG, PSR can omit all operands as long
+   as a valid operand symbol. As of v10.5.0, PSR can omit all operands as long
    as there is at least one whitespace character between the variable name and the version.
 
 3. The value of the variable must match a `SemVer`_ regular expression and can be

pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-semantic-release"
-version = "10.4.1"
+version = "10.5.0"
 description = "Automatic Semantic Versioning for Python projects"
 requires-python = "~= 3.8"
 license = { text = "MIT" }

src/gh_action/requirements.txt

@@ -1 +1 @@
-python-semantic-release == 10.4.1
+python-semantic-release == 10.5.0