python-semantic-release 9.20.0__tar.gz → 9.21.1__tar.gz

{python_semantic_release-9.20.0/src/python_semantic_release.egg-info → python_semantic_release-9.21.1}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: python-semantic-release
-Version: 9.20.0
+Version: 9.21.1
 Summary: Automatic Semantic Versioning for Python projects
 Author-email: Rolf Erik Lekang <me@rolflekang.com>
 License: MIT
@@ -26,12 +26,12 @@ Requires-Dist: click-option-group~=0.5
 Requires-Dist: gitpython~=3.0
 Requires-Dist: requests~=2.25
 Requires-Dist: jinja2~=3.1
-Requires-Dist: python-gitlab~=4.0
+Requires-Dist: python-gitlab<6.0.0,>=4.0.0
 Requires-Dist: tomlkit~=0.11
 Requires-Dist: dotty-dict~=1.3
 Requires-Dist: importlib-resources~=6.0
 Requires-Dist: pydantic~=2.0
-Requires-Dist: rich~=13.0
+Requires-Dist: rich~=14.0
 Requires-Dist: shellingham~=1.5
 Requires-Dist: Deprecated~=1.2
 Provides-Extra: build
@@ -49,7 +49,7 @@ Requires-Dist: freezegun~=1.5; extra == "test"
 Requires-Dist: pyyaml~=6.0; extra == "test"
 Requires-Dist: pytest~=8.3; extra == "test"
 Requires-Dist: pytest-clarity~=1.0; extra == "test"
-Requires-Dist: pytest-cov~=5.0; extra == "test"
+Requires-Dist: pytest-cov<7.0.0,>=5.0.0; extra == "test"
 Requires-Dist: pytest-env~=1.0; extra == "test"
 Requires-Dist: pytest-lazy-fixtures~=1.1.1; extra == "test"
 Requires-Dist: pytest-mock~=3.0; extra == "test"
@@ -67,6 +67,7 @@ Requires-Dist: mypy==1.15.0; extra == "mypy"
 Requires-Dist: types-Deprecated~=1.2; extra == "mypy"
 Requires-Dist: types-requests~=2.32.0; extra == "mypy"
 Requires-Dist: types-pyyaml~=6.0; extra == "mypy"
+Dynamic: license-file
 
 Python Semantic Release
 ***********************

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/docs/automatic-releases/github-actions.rst

@@ -337,7 +337,7 @@ before the :ref:`version <cmd-version>` subcommand.
 
   .. code:: yaml
 
-    - uses: python-semantic-release/python-semantic-release@v9.19.1
+    - uses: python-semantic-release/python-semantic-release@v9.21.0
       with:
         root_options: "-vv --noop"
 
@@ -576,7 +576,7 @@ before the :ref:`publish <cmd-publish>` subcommand.
 
   .. code:: yaml
 
-    - uses: python-semantic-release/publish-action@v9.19.1
+    - uses: python-semantic-release/publish-action@v9.21.0
       with:
         root_options: "-vv --noop"
 
@@ -643,7 +643,7 @@ Examples
 Common Workflow Example
 -----------------------
 
-The following is a common workflow example that uses both the Python Semantic Release Action
+The following is a simple common workflow example that uses both the Python Semantic Release Action
 and the Python Semantic Release Publish Action. This workflow will run on every push to the
 ``main`` branch and will create a new release upon a successful version determination. If a
 version is released, the workflow will then publish the package to PyPI and upload the package
@@ -661,51 +661,100 @@ to the GitHub Release Assets as well.
     jobs:
       release:
         runs-on: ubuntu-latest
-        concurrency: release
+        concurrency:
+          group: ${{ github.workflow }}-release-${{ github.ref_name }}
+          cancel-in-progress: false
 
         permissions:
           id-token: write
           contents: write
 
         steps:
-          # Note: we need to checkout the repository at the workflow sha in case during the workflow
-          # the branch was updated. To keep PSR working with the configured release branches,
-          # we force a checkout of the desired release branch but at the workflow sha HEAD.
-          - name: Setup | Checkout Repository at workflow sha
+          # Note: We checkout the repository at the branch that triggered the workflow
+          # with the entire history to ensure to match PSR's release branch detection
+          # and history evaluation.
+          # However, we forcefully reset the branch to the workflow sha because it is
+          # possible that the branch was updated while the workflow was running. This
+          # prevents accidentally releasing un-evaluated changes.
+          - name: Setup | Checkout Repository on Release Branch
             uses: actions/checkout@v4
             with:
+              ref: ${{ github.ref_name }}
               fetch-depth: 0
-              ref: ${{ github.sha }}
 
-          - name: Setup | Force correct release branch on workflow sha
+          - name: Setup | Force release branch to be at workflow sha
             run: |
-              git checkout -B ${{ github.ref_name }} ${{ github.sha }}
+              git reset --hard ${{ github.sha }}
+
+          - name: Evaluate | Verify upstream has NOT changed
+            # Last chance to abort before causing an error as another PR/push was applied to
+            # the upstream branch while this workflow was running. This is important
+            # because we are committing a version change (--commit). You may omit this step
+            # if you have 'commit: false' in your configuration.
+            #
+            # You may consider moving this to a repo script and call it from this step instead
+            # of writing it in-line.
+            shell: bash
+            run: |
+              set +o pipefail
+
+              UPSTREAM_BRANCH_NAME="$(git status -sb | head -n 1 | cut -d' ' -f2 | grep -E '\.{3}' | cut -d'.' -f4)"
+              printf '%s\n' "Upstream branch name: $UPSTREAM_BRANCH_NAME"
+
+              set -o pipefail
+
+              if [ -z "$UPSTREAM_BRANCH_NAME" ]; then
+                  printf >&2 '%s\n' "::error::Unable to determine upstream branch name!"
+                  exit 1
+              fi
+
+              git fetch "${UPSTREAM_BRANCH_NAME%%/*}"
+
+              if ! UPSTREAM_SHA="$(git rev-parse "$UPSTREAM_BRANCH_NAME")"; then
+                  printf >&2 '%s\n' "::error::Unable to determine upstream branch sha!"
+                  exit 1
+              fi
+
+              HEAD_SHA="$(git rev-parse HEAD)"
+
+              if [ "$HEAD_SHA" != "$UPSTREAM_SHA" ]; then
+                  printf >&2 '%s\n' "[HEAD SHA] $HEAD_SHA != $UPSTREAM_SHA [UPSTREAM SHA]"
+                  printf >&2 '%s\n' "::error::Upstream has changed, aborting release..."
+                  exit 1
+              fi
+
+              printf '%s\n' "Verified upstream branch has not changed, continuing with release..."
 
           - name: Action | Semantic Version Release
             id: release
             # Adjust tag with desired version if applicable.
-            uses: python-semantic-release/python-semantic-release@v9.19.1
+            uses: python-semantic-release/python-semantic-release@v9.21.0
             with:
               github_token: ${{ secrets.GITHUB_TOKEN }}
               git_committer_name: "github-actions"
               git_committer_email: "actions@users.noreply.github.com"
 
-          - name: Publish | Upload package to PyPI
-            uses: pypa/gh-action-pypi-publish@v1
-            if: steps.release.outputs.released == 'true'
-
           - name: Publish | Upload to GitHub Release Assets
-            uses: python-semantic-release/publish-action@v9.19.1
+            uses: python-semantic-release/publish-action@v9.21.0
             if: steps.release.outputs.released == 'true'
             with:
               github_token: ${{ secrets.GITHUB_TOKEN }}
               tag: ${{ steps.release.outputs.tag }}
 
+          - name: Publish | Upload package to PyPI
+            uses: pypa/gh-action-pypi-publish@SHA1_HASH  # vX.X.X
+            if: steps.release.outputs.released == 'true'
+
 .. important::
   The `concurrency`_ directive is used on the job to prevent race conditions of more than
   one release job in the case if there are multiple pushes to ``main`` in a short period
   of time.
 
+  Secondly the *Evaluate | Verify upstream has NOT changed* step is used to ensure that the
+  upstream branch has not changed while the workflow was running. This is important because
+  we are committing a version change (``commit: true``) and there might be a push collision
+  that would cause undesired behavior. Review Issue `#1201`_ for more detailed information.
+
 .. warning::
   You must set ``fetch-depth`` to 0 when using ``actions/checkout@v4``, since
   Python Semantic Release needs access to the full history to build a changelog
@@ -721,6 +770,7 @@ to the GitHub Release Assets as well.
   case, you will also need to pass the new token to ``actions/checkout`` (as
   the ``token`` input) in order to gain push access.
 
+.. _#1201: https://github.com/python-semantic-release/python-semantic-release/issues/1201
 .. _concurrency: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idconcurrency
 
 Version Overrides Example
@@ -744,7 +794,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@v9.19.1
+    uses: python-semantic-release/python-semantic-release@v9.21.0
     with:
       github_token: ${{ secrets.GITHUB_TOKEN }}
       force: patch
@@ -766,19 +816,84 @@ For multiple packages, you would need to run the action multiple times, to relea
 each project. The following example demonstrates how to release two projects in
 a monorepo.
 
+Remember that for each release of each submodule you will then need to handle publishing
+each package separately as well. This is dependent on the result of your build commands.
+In the example below, we assume a simple ``build`` module command to build a ``sdist``
+and wheel artifacts into the submodule's ``dist`` directory.
+
 The ``directory`` input directive is also available for the Python Semantic Release
 Publish Action.
 
 .. code:: yaml
 
-   - name: Release Project 1
-     uses: python-semantic-release/python-semantic-release@v9.19.1
-     with:
-       directory: ./project1
-       github_token: ${{ secrets.GITHUB_TOKEN }}
-
-   - name: Release Project 2
-     uses: python-semantic-release/python-semantic-release@v9.19.1
-     with:
-       directory: ./project2
-       github_token: ${{ secrets.GITHUB_TOKEN }}
+  jobs:
+
+    release:
+
+      env:
+        SUBMODULE_1_DIR: project1
+        SUBMODULE_2_DIR: project2
+
+      steps:
+
+        # ------------------------------------------------------------------- #
+        # Note the use of different IDs to distinguish which submodule was    #
+        # identified to be released. The subsequent actions then reference    #
+        # their specific release ID to determine if a release occurred.       #
+        # ------------------------------------------------------------------- #
+
+        - name: Release submodule 1
+          id: release-submod-1
+          uses: python-semantic-release/python-semantic-release@v9.21.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@v9.21.0
+          with:
+            directory: ${{ env.SUBMODULE_2_DIR }}
+            github_token: ${{ secrets.GITHUB_TOKEN }}
+
+        # ------------------------------------------------------------------- #
+        # For each submodule, you will have to publish the package separately #
+        # and only attempt to publish if the release for that submodule was   #
+        # deemed a release (and the release was successful).                  #
+        # ------------------------------------------------------------------- #
+
+        - name: Publish | Upload package 1 to GitHub Release Assets
+          uses: python-semantic-release/publish-action@v9.21.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@v9.21.0
+          if: steps.release-submod-2.outputs.released == 'true'
+          with:
+            directory: ${{ env.SUBMODULE_2_DIR }}
+            github_token: ${{ secrets.GITHUB_TOKEN }}
+            tag: ${{ steps.release-submod-2.outputs.tag }}
+
+        # ------------------------------------------------------------------- #
+        # Python Semantic Release is not responsible for publishing your      #
+        # python artifacts to PyPI. Use the official PyPA publish action      #
+        # instead. The following steps are an example but is not guaranteed   #
+        # to work as the action is not maintained by the                      #
+        # python-semantic-release team.                                       #
+        # ------------------------------------------------------------------- #
+
+        - name: Publish | Upload package 1 to PyPI
+          uses: pypa/gh-action-pypi-publish@SHA1_HASH  # vX.X.X
+          if: steps.release-submod-1.outputs.released == 'true'
+          with:
+            packages-dir: ${{ format('{}/dist', env.SUBMODULE_1_DIR) }}
+
+        - name: Publish | Upload package 2 to PyPI
+          uses: pypa/gh-action-pypi-publish@SHA1_HASH  # vX.X.X
+          if: steps.release-submod-2.outputs.released == 'true'
+          with:
+            packages-dir: ${{ format('{}/dist', env.SUBMODULE_2_DIR) }}

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/docs/configuration.rst

@@ -1209,9 +1209,9 @@ within the TOML file, which is more accurate than a pattern replace.
 The ``version_toml`` option is commonly used to update the version number in the project
 definition file: ``pyproject.toml`` as seen in the example below.
 
-As of ${NEW_RELEASE_TAG}, the ``version_toml`` option accepts a colon-separated definition
+As of v9.20.0, the ``version_toml`` option accepts a colon-separated definition
 with either 2 or 3 parts. The 2-part definition includes the file path and the version
-parameter (in dot-notation). Newly with ${NEW_RELEASE_TAG}, it also accepts an optional
+parameter (in dot-notation). Newly with v9.20.0, it also accepts an optional
 3rd part to allow configuration of the format type.
 
 **Available Format Types**
@@ -1271,9 +1271,9 @@ The ``version_variables`` configuration option is a list of string definitions
 that defines where the version number should be updated in the repository, when
 a new version is released.
 
-As of ${NEW_RELEASE_TAG}, the ``version_variables`` option accepts a
+As of v9.20.0, the ``version_variables`` option accepts a
 colon-separated definition with either 2 or 3 parts. The 2-part definition includes
-the file path and the variable name. Newly with ${NEW_RELEASE_TAG}, it also accepts
+the file path and the variable name. Newly with v9.20.0, it also accepts
 an optional 3rd part to allow configuration of the format type.
 
 **Available Format Types**
@@ -1283,7 +1283,7 @@ an optional 3rd part to allow configuration of the format type.
 
 If the format type is not specified, it will default to the number format.
 
-Prior to ${NEW_RELEASE_TAG}, PSR only supports entries with the first 2-parts
+Prior to v9.20.0, PSR only supports entries with the first 2-parts
 as the tag format type was not available and would only replace numeric
 version numbers.
 

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/pyproject.toml

@@ -1,12 +1,12 @@
 # Ref: https://packaging.python.org/en/latest/specifications/declaring-project-metadata/
 # and https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html
 [build-system]
-requires = ["setuptools ~= 75.3.0", "wheel ~= 0.42"]
+requires = ["setuptools >= 75.3.0, < 81.0.0", "wheel ~= 0.42"]
 build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-semantic-release"
-version = "9.20.0"
+version = "9.21.1"
 description = "Automatic Semantic Versioning for Python projects"
 requires-python = ">=3.8"
 license = { text = "MIT" }
@@ -28,17 +28,18 @@ dependencies = [
   "gitpython ~= 3.0",
   "requests ~= 2.25",
   "jinja2 ~= 3.1",
-  "python-gitlab ~= 4.0",
+  "python-gitlab >= 4.0.0, < 6.0.0",
   "tomlkit ~= 0.11",
   "dotty-dict ~= 1.3",
   "importlib-resources ~= 6.0",
   "pydantic ~= 2.0",
-  "rich ~= 13.0",
+  "rich ~= 14.0",
   "shellingham ~= 1.5",
   "Deprecated ~= 1.2",  # Backport of deprecated decorator for python 3.8
 ]
 
 [project.scripts]
+python-semantic-release = "semantic_release.__main__:main"
 semantic-release = "semantic_release.__main__:main"
 psr = "semantic_release.__main__:main"
 
@@ -67,7 +68,7 @@ test = [
   "pyyaml ~= 6.0",
   "pytest ~= 8.3",
   "pytest-clarity ~= 1.0",
-  "pytest-cov ~= 5.0",
+  "pytest-cov >= 5.0.0, < 7.0.0",
   "pytest-env ~= 1.0",
   "pytest-lazy-fixtures ~= 1.1.1",
   "pytest-mock ~= 3.0",
@@ -411,7 +412,6 @@ build_command = """
     python -m build .
 """
 major_on_zero = true
-version_variables = ["src/semantic_release/__init__.py:__version__"]
 version_toml = ["pyproject.toml:project.version"]
 
 [tool.semantic_release.changelog]

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1/src/python_semantic_release.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: python-semantic-release
-Version: 9.20.0
+Version: 9.21.1
 Summary: Automatic Semantic Versioning for Python projects
 Author-email: Rolf Erik Lekang <me@rolflekang.com>
 License: MIT
@@ -26,12 +26,12 @@ Requires-Dist: click-option-group~=0.5
 Requires-Dist: gitpython~=3.0
 Requires-Dist: requests~=2.25
 Requires-Dist: jinja2~=3.1
-Requires-Dist: python-gitlab~=4.0
+Requires-Dist: python-gitlab<6.0.0,>=4.0.0
 Requires-Dist: tomlkit~=0.11
 Requires-Dist: dotty-dict~=1.3
 Requires-Dist: importlib-resources~=6.0
 Requires-Dist: pydantic~=2.0
-Requires-Dist: rich~=13.0
+Requires-Dist: rich~=14.0
 Requires-Dist: shellingham~=1.5
 Requires-Dist: Deprecated~=1.2
 Provides-Extra: build
@@ -49,7 +49,7 @@ Requires-Dist: freezegun~=1.5; extra == "test"
 Requires-Dist: pyyaml~=6.0; extra == "test"
 Requires-Dist: pytest~=8.3; extra == "test"
 Requires-Dist: pytest-clarity~=1.0; extra == "test"
-Requires-Dist: pytest-cov~=5.0; extra == "test"
+Requires-Dist: pytest-cov<7.0.0,>=5.0.0; extra == "test"
 Requires-Dist: pytest-env~=1.0; extra == "test"
 Requires-Dist: pytest-lazy-fixtures~=1.1.1; extra == "test"
 Requires-Dist: pytest-mock~=3.0; extra == "test"
@@ -67,6 +67,7 @@ Requires-Dist: mypy==1.15.0; extra == "mypy"
 Requires-Dist: types-Deprecated~=1.2; extra == "mypy"
 Requires-Dist: types-requests~=2.32.0; extra == "mypy"
 Requires-Dist: types-pyyaml~=6.0; extra == "mypy"
+Dynamic: license-file
 
 Python Semantic Release
 ***********************

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/src/python_semantic_release.egg-info/entry_points.txt

@@ -1,3 +1,4 @@
 [console_scripts]
 psr = semantic_release.__main__:main
+python-semantic-release = semantic_release.__main__:main
 semantic-release = semantic_release.__main__:main

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/src/python_semantic_release.egg-info/requires.txt

@@ -3,12 +3,12 @@ click-option-group~=0.5
 gitpython~=3.0
 requests~=2.25
 jinja2~=3.1
-python-gitlab~=4.0
+python-gitlab<6.0.0,>=4.0.0
 tomlkit~=0.11
 dotty-dict~=1.3
 importlib-resources~=6.0
 pydantic~=2.0
-rich~=13.0
+rich~=14.0
 shellingham~=1.5
 Deprecated~=1.2
 
@@ -40,7 +40,7 @@ freezegun~=1.5
 pyyaml~=6.0
 pytest~=8.3
 pytest-clarity~=1.0
-pytest-cov~=5.0
+pytest-cov<7.0.0,>=5.0.0
 pytest-env~=1.0
 pytest-lazy-fixtures~=1.1.1
 pytest-mock~=3.0

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/src/semantic_release/__init__.py

@@ -2,6 +2,8 @@
 
 from __future__ import annotations
 
+import importlib.metadata
+
 from semantic_release.commit_parser import (
     CommitParser,
     ParsedCommit,
@@ -24,7 +26,7 @@ from semantic_release.version import (
     tags_and_versions,
 )
 
-__version__ = "9.20.0"
+__version__ = importlib.metadata.version(f"python_{__package__}".replace("_", "-"))
 
 __all__ = [
     "CommitParser",

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/src/semantic_release/hvcs/remote_hvcs_base.py

@@ -95,10 +95,15 @@ class RemoteHvcsBase(HvcsBase, metaclass=ABCMeta):
         query: str | None = None,
         fragment: str | None = None,
     ) -> str:
-        # Ensure any path prefix is transfered but not doubled up on the derived url
+        # Ensure any path prefix is transferred but not doubled up on the derived url
+        normalized_path = (
+            f"{self.hvcs_domain.path}/{path}"
+            if self.hvcs_domain.path and not path.startswith(self.hvcs_domain.path)
+            else path
+        )
         return self._derive_url(
             self.hvcs_domain,
-            path=f"{self.hvcs_domain.path or ''}/{path.lstrip(self.hvcs_domain.path)}",
+            path=normalized_path,
             auth=auth,
             query=query,
             fragment=fragment,
@@ -123,10 +128,15 @@ class RemoteHvcsBase(HvcsBase, metaclass=ABCMeta):
         query: str | None = None,
         fragment: str | None = None,
     ) -> str:
-        # Ensure any api path prefix is transfered but not doubled up on the derived api url
+        # Ensure any api path prefix is transferred but not doubled up on the derived api url
+        normalized_endpoint = (
+            f"{self.api_url.path}/{endpoint}"
+            if self.api_url.path and not endpoint.startswith(self.api_url.path)
+            else endpoint
+        )
         return self._derive_url(
             self.api_url,
-            path=f"{self.api_url.path or ''}/{endpoint.lstrip(self.api_url.path)}",
+            path=normalized_endpoint,
             auth=auth,
             query=query,
             fragment=fragment,

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/tests/e2e/test_main.py

@@ -1,6 +1,7 @@
 from __future__ import annotations
 
 import json
+import subprocess
 from pathlib import Path
 from textwrap import dedent
 from typing import TYPE_CHECKING
@@ -12,7 +13,7 @@ from pytest_lazy_fixtures.lazy_fixture import lf as lazy_fixture
 from semantic_release import __version__
 from semantic_release.cli.commands.main import main
 
-from tests.const import MAIN_PROG_NAME, VERSION_SUBCMD
+from tests.const import MAIN_PROG_NAME, SUCCESS_EXIT_CODE, VERSION_SUBCMD
 from tests.fixtures.repos import repo_w_no_tags_conventional_commits
 from tests.util import assert_exit_code, assert_successful_exit_code
 
@@ -25,6 +26,30 @@ if TYPE_CHECKING:
     from tests.fixtures.git_repo import BuiltRepoResult
 
 
+@pytest.mark.parametrize(
+    "project_script_name",
+    [
+        "python-semantic-release",
+        "semantic-release",
+        "psr",
+    ],
+)
+def test_entrypoint_scripts(project_script_name: str):
+    # Setup
+    command = str.join(" ", [project_script_name, "--version"])
+    expected_output = f"semantic-release, version {__version__}\n"
+
+    # Act
+    proc = subprocess.run(  # noqa: S602, PLW1510
+        command, shell=True, text=True, capture_output=True
+    )
+
+    # Evaluate
+    assert SUCCESS_EXIT_CODE == proc.returncode  # noqa: SIM300
+    assert expected_output == proc.stdout
+    assert not proc.stderr
+
+
 def test_main_prints_version_and_exits(cli_runner: CliRunner):
     cli_cmd = [MAIN_PROG_NAME, "--version"]
 

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/tests/unit/semantic_release/hvcs/test_bitbucket.py

@@ -301,6 +301,29 @@ def test_commit_hash_url(default_bitbucket_client: Bitbucket):
     assert expected_url == default_bitbucket_client.commit_hash_url(sha)
 
 
+def test_commit_hash_url_w_custom_server():
+    """
+    Test the commit hash URL generation for a self-hosted Bitbucket server with prefix.
+
+    ref: https://github.com/python-semantic-release/python-semantic-release/issues/1204
+    """
+    sha = "244f7e11bcb1e1ce097db61594056bc2a32189a0"
+    expected_url = "{server}/{owner}/{repo}/commits/{sha}".format(
+        server=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo",
+        owner="foo",
+        repo=EXAMPLE_REPO_NAME,
+        sha=sha,
+    )
+
+    with mock.patch.dict(os.environ, {}, clear=True):
+        actual_url = Bitbucket(
+            remote_url=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo/foo/{EXAMPLE_REPO_NAME}.git",
+            hvcs_domain=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo",
+        ).commit_hash_url(sha)
+
+    assert expected_url == actual_url
+
+
 @pytest.mark.parametrize("pr_number", (666, "666", "#666"))
 def test_pull_request_url(default_bitbucket_client: Bitbucket, pr_number: int | str):
     expected_url = "{server}/{owner}/{repo}/pull-requests/{pr_number}".format(

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/tests/unit/semantic_release/hvcs/test_gitea.py

@@ -203,6 +203,29 @@ def test_commit_hash_url(default_gitea_client: Gitea):
     assert expected_url == default_gitea_client.commit_hash_url(sha)
 
 
+def test_commit_hash_url_w_custom_server():
+    """
+    Test the commit hash URL generation for a self-hosted Bitbucket server with prefix.
+
+    ref: https://github.com/python-semantic-release/python-semantic-release/issues/1204
+    """
+    sha = "244f7e11bcb1e1ce097db61594056bc2a32189a0"
+    expected_url = "{server}/{owner}/{repo}/commit/{sha}".format(
+        server=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo",
+        owner="foo",
+        repo=EXAMPLE_REPO_NAME,
+        sha=sha,
+    )
+
+    with mock.patch.dict(os.environ, {}, clear=True):
+        actual_url = Gitea(
+            remote_url=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo/foo/{EXAMPLE_REPO_NAME}.git",
+            hvcs_domain=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo",
+        ).commit_hash_url(sha)
+
+    assert expected_url == actual_url
+
+
 @pytest.mark.parametrize("issue_number", (666, "666", "#666"))
 def test_issue_url(default_gitea_client: Gitea, issue_number: int | str):
     expected_url = "{server}/{owner}/{repo}/issues/{issue_number}".format(

{python_semantic_release-9.20.0 → python_semantic_release-9.21.1}/tests/unit/semantic_release/hvcs/test_github.py

@@ -375,6 +375,29 @@ def test_commit_hash_url(default_gh_client: Github):
     assert expected_url == default_gh_client.commit_hash_url(sha)
 
 
+def test_commit_hash_url_w_custom_server():
+    """
+    Test the commit hash URL generation for a self-hosted Bitbucket server with prefix.
+
+    ref: https://github.com/python-semantic-release/python-semantic-release/issues/1204
+    """
+    sha = "244f7e11bcb1e1ce097db61594056bc2a32189a0"
+    expected_url = "{server}/{owner}/{repo}/commit/{sha}".format(
+        server=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo",
+        owner="foo",
+        repo=EXAMPLE_REPO_NAME,
+        sha=sha,
+    )
+
+    with mock.patch.dict(os.environ, {}, clear=True):
+        actual_url = Github(
+            remote_url=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo/foo/{EXAMPLE_REPO_NAME}.git",
+            hvcs_domain=f"https://{EXAMPLE_HVCS_DOMAIN}/projects/demo-foo",
+        ).commit_hash_url(sha)
+
+    assert expected_url == actual_url
+
+
 @pytest.mark.parametrize("issue_number", (666, "666", "#666"))
 def test_issue_url(default_gh_client: Github, issue_number: str | int):
     expected_url = "{server}/{owner}/{repo}/issues/{issue_num}".format(