python-semantic-release 9.16.1__tar.gz → 9.17.0__tar.gz

{python_semantic_release-9.16.1/src/python_semantic_release.egg-info → python_semantic_release-9.17.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: python-semantic-release
-Version: 9.16.1
+Version: 9.17.0
 Summary: Automatic Semantic Versioning for Python projects
 Author-email: Rolf Erik Lekang <me@rolflekang.com>
 License: MIT

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/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.16.0
+    - uses: python-semantic-release/python-semantic-release@v9.16.1
       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.16.0
+    - uses: python-semantic-release/publish-action@v9.16.1
       with:
         root_options: "-vv --noop"
 
@@ -684,7 +684,7 @@ 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@v9.16.0
+            uses: python-semantic-release/python-semantic-release@v9.16.1
             with:
               github_token: ${{ secrets.GITHUB_TOKEN }}
               git_committer_name: "github-actions"
@@ -695,7 +695,7 @@ to the GitHub Release Assets as well.
             if: steps.release.outputs.released == 'true'
 
           - name: Publish | Upload to GitHub Release Assets
-            uses: python-semantic-release/publish-action@v9.16.0
+            uses: python-semantic-release/publish-action@v9.16.1
             if: steps.release.outputs.released == 'true'
             with:
               github_token: ${{ secrets.GITHUB_TOKEN }}
@@ -744,7 +744,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.16.0
+    uses: python-semantic-release/python-semantic-release@v9.16.1
     with:
       github_token: ${{ secrets.GITHUB_TOKEN }}
       force: patch
@@ -772,13 +772,13 @@ Publish Action.
 .. code:: yaml
 
    - name: Release Project 1
-     uses: python-semantic-release/python-semantic-release@v9.16.0
+     uses: python-semantic-release/python-semantic-release@v9.16.1
      with:
        directory: ./project1
        github_token: ${{ secrets.GITHUB_TOKEN }}
 
    - name: Release Project 2
-     uses: python-semantic-release/python-semantic-release@v9.16.0
+     uses: python-semantic-release/python-semantic-release@v9.16.1
      with:
        directory: ./project2
        github_token: ${{ secrets.GITHUB_TOKEN }}

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/docs/changelog_templates.rst

@@ -831,6 +831,31 @@ The filters provided vary based on the VCS configured and available features:
       {% set prev_changelog_contents = prev_changelog_file | read_file | safe %}
 
 
+* ``sort_numerically (Callable[[Iterable[str], bool], list[str]])``: given a
+  sequence of strings with possibly some non-number characters as a prefix or suffix,
+  sort the strings as if they were just numbers from lowest to highest. This filter
+  is useful when you want to sort issue numbers or other strings that have a numeric
+  component in them but cannot be cast to a number directly to sort them. If you want
+  to sort the strings in reverse order, you can pass a boolean value of ``True`` as the
+  second argument.
+
+  *Introduced in v9.16.0.*
+
+  **Example Usage:**
+
+  .. code:: jinja
+
+      {{ ["#222", "#1023", "#444"] | sort_numerically }}
+      {{ ["#222", "#1023", "#444"] | sort_numerically(True) }}
+
+  **Markdown Output:**
+
+  .. code:: markdown
+
+        ['#222', '#444', '#1023']
+        ['#1023', '#444', '#222']
+
+
 Availability of the documented filters can be found in the table below:
 
 ======================  =========  =====  ======  ======
@@ -846,6 +871,7 @@ issue_url                  ❌       ✅      ✅      ✅
 merge_request_url          ❌       ❌      ❌      ✅
 pull_request_url           ✅       ✅      ✅      ✅
 read_file                  ✅       ✅      ✅      ✅
+sort_numerically           ✅       ✅      ✅      ✅
 ======================  =========  =====  ======  ======
 
 .. seealso::

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/docs/commit_parsing.rst

@@ -108,13 +108,13 @@ logic in relation to how PSR's core features:
   message. If no issue numbers are found, the parser will return an empty tuple. *Feature
   available in v9.15.0+.*
 
-**Limitations:**
+- **Squash Commit Evaluation**: This parser implements PSR's
+  :ref:`commit_parser-builtin-squash_commit_evaluation` to identify and extract each commit
+  message as a separate commit message within a single squashed commit. You can toggle this
+  feature on/off via the :ref:`config-commit_parser_options` setting. *Feature available in
+  v9.17.0+.*
 
-- Squash commits are not currently supported. This means that the level bump for a squash
-  commit is only determined by the subject line of the squash commit. Our default changelog
-  template currently writes out the entire commit message body in the changelog in order to
-  provide the full detail of the changes. Track the implementation of this feature with
-  the issues `#733`_, `#1085`_, and `PR#1112`_.
+**Limitations**:
 
 - Commits with the ``revert`` type are not currently supported. Track the implementation
   of this feature in the issue `#402`_.
@@ -179,6 +179,12 @@ how PSR's core features:
   enabled by setting the configuration option ``commit_parser_options.parse_linked_issues``
   to ``true``. *Feature available in v9.15.0+.*
 
+- **Squash Commit Evaluation**: This parser implements PSR's
+  :ref:`commit_parser-builtin-squash_commit_evaluation` to identify and extract each commit
+  message as a separate commit message within a single squashed commit. You can toggle this
+  feature on/off via the :ref:`config-commit_parser_options` setting. *Feature available in
+  v9.17.0+.*
+
 If no commit parser options are provided via the configuration, the parser will use PSR's
 built-in :py:class:`defaults <semantic_release.commit_parser.emoji.EmojiParserOptions>`.
 
@@ -304,6 +310,72 @@ return an empty tuple.
 
 ----
 
+.. _commit_parser-builtin-squash_commit_evaluation:
+
+Common Squash Commit Evaluation
+"""""""""""""""""""""""""""""""
+
+*Introduced in v9.17.0*
+
+All of the PSR built-in parsers implement common squash commit evaluation logic to identify
+and extract individual commit messages from a single squashed commit. The parsers will
+look for common squash commit delimiters and multiple matches of the commit message
+format to identify each individual commit message that was squashed. The parsers will
+return a list containing each commit message as a separate commit object. Squashed commits
+will be evaluated individually for both the level bump and changelog generation. If no
+squash commits are found, a list with the single commit object will be returned.
+
+Currently, PSR has been tested against GitHub, BitBucket, and official ``git`` squash
+merge commmit messages. GitLab does not have a default template for squash commit messages
+but can be customized per project or server. If you are using GitLab, you will need to
+ensure that the squash commit message format is similar to the example below.
+
+**Example**:
+
+*The following example will extract three separate commit messages from a single GitHub
+formatted squash commit message of conventional commit style:*
+
+.. code-block:: text
+
+    feat(config): add new config option (#123)
+
+    * refactor(config): change the implementation of config loading
+
+    * docs(configuration): defined new config option for the project
+
+When parsed with the default angular parser with squash commits toggled on, the version
+bump will be determined by the highest level bump of the three commits (in this case, a
+minor bump because of the feature commit) and the release notes would look similar to
+the following:
+
+.. code-block:: markdown
+
+    ## Features
+
+    - **config**: add new config option (#123)
+
+    ## Documentation
+
+    - **configuration**: defined new config option for the project (#123)
+
+    ## Refactoring
+
+    - **config**: change the implementation of config loading (#123)
+
+Merge request numbers and commit hash values will be the same across all extracted
+commits. Additionally, any :ref:`config-changelog-exclude_commit_patterns` will be
+applied individually to each extracted commit so if you are have an exclusion match
+for ignoring ``refactor`` commits, the second commit in the example above would be
+excluded from the changelog.
+
+.. important::
+  When squash commit evaluation is enabled, if you squashed a higher level bump commit
+  into the body of a lower level bump commit, the higher level bump commit will be
+  evaluated as the level bump for the entire squashed commit. This includes breaking
+  change descriptions.
+
+----
+
 .. _commit_parser-builtin-customization:
 
 Customization
@@ -429,28 +501,23 @@ available.
 .. _catching exceptions in Python is slower: https://docs.python.org/3/faq/design.html#how-fast-are-exceptions
 .. _namedtuple: https://docs.python.org/3/library/typing.html#typing.NamedTuple
 
-.. _commit-parsing-parser-options:
+.. _commit_parser-parser-options:
 
 Parser Options
 """"""""""""""
 
-To provide options to the commit parser which is configured in the :ref:`configuration file
-<configuration>`, Python Semantic Release includes a
-:py:class:`ParserOptions <semantic_release.commit_parser._base.ParserOptions>`
-class. Each parser built into Python Semantic Release has a corresponding "options" class, which
-subclasses :py:class:`ParserOptions <semantic_release.commit_parser._base.ParserOptions>`.
-
-The configuration in :ref:`commit_parser_options <config-commit_parser_options>` is passed to the
-"options" class which is specified by the configured :ref:`commit_parser <config-commit_parser>` -
-more information on how this is specified is below.
+When writing your own parser, you should accompany the parser with an "options" class
+which accepts the appropriate keyword arguments. This class' ``__init__`` method should
+store the values that are needed for parsing appropriately. Python Semantic Release will
+pass any configuration options from the configuration file's
+:ref:`commit_parser_options <config-commit_parser_options>`, into your custom parser options
+class. To ensure that the configuration options are passed correctly, the options class
+should inherit from the
+:py:class:`ParserOptions <semantic_release.commit_parser._base.ParserOptions>` class.
 
 The "options" class is used to validate the options which are configured in the repository,
 and to provide default values for these options where appropriate.
 
-If you are writing your own parser, you should accompany it with an "options" class
-which accepts the appropriate keyword arguments. This class' ``__init__`` method should
-store the values that are needed for parsing appropriately.
-
 .. _commit-parsing-commit-parsers:
 
 Commit Parsers

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/docs/configuration.rst

@@ -811,66 +811,14 @@ For more information see :ref:`commit-parsing`.
 
 **Type:** ``dict[str, Any]``
 
-These options are passed directly to the ``parser_options`` method of
-:ref:`the commit parser <config-commit_parser>`, without validation
-or transformation.
+This set of options are passed directly to the commit parser class specified in
+:ref:`the commit parser <config-commit_parser>` configuration option.
 
-For more information, see :ref:`commit-parsing-parser-options`.
-
-The default value for this setting depends on what you specify as
-:ref:`commit_parser <config-commit_parser>`. The table below outlines
-the expections from ``commit_parser`` value to default options value.
-
-==================  ==   =================================
-``commit_parser``        Default ``commit_parser_options``
-==================  ==   =================================
-``"angular"``       ->   .. code-block:: toml
-
-                             [semantic_release.commit_parser_options]
-                             allowed_types = [
-                                 "build", "chore", "ci", "docs", "feat", "fix",
-                                 "perf", "style", "refactor", "test"
-                             ]
-                             minor_types = ["feat"]
-                             patch_types = ["fix", "perf"]
-
-``"emoji"``         ->   .. code-block:: toml
-
-                             [semantic_release.commit_parser_options]
-                             major_tags = [":boom:"]
-                             minor_tags = [
-                                 ":sparkles:", ":children_crossing:", ":lipstick:",
-                                 ":iphone:", ":egg:", ":chart_with_upwards_trend:"
-                             ]
-                             patch_tags = [
-                                 ":ambulance:", ":lock:", ":bug:", ":zap:", ":goal_net:",
-                                 ":alien:", ":wheelchair:", ":speech_balloon:", ":mag:",
-                                 ":apple:", ":penguin:", ":checkered_flag:", ":robot:",
-                                 ":green_apple:"
-                             ]
-
-``"scipy"``         ->   .. code-block:: toml
-
-                             [semantic_release.commit_parser_options]
-                             allowed_tags = [
-                                "API", "DEP", "ENH", "REV", "BUG", "MAINT", "BENCH",
-                                "BLD", "DEV", "DOC", "STY", "TST", "REL", "FEAT", "TEST",
-                             ]
-                             major_tags = ["API",]
-                             minor_tags = ["DEP", "DEV", "ENH", "REV", "FEAT"]
-                             patch_tags = ["BLD", "BUG", "MAINT"]
-
-``"tag"``           ->   .. code-block:: toml
-
-                             [semantic_release.commit_parser_options]
-                             minor_tag = ":sparkles:"
-                             patch_tag = ":nut_and_bolt:"
-
-``"module:class"``  ->   ``**module:class.parser_options()``
-==================  ==   =================================
+For more information (to include defaults), see
+:ref:`commit_parser-builtin-customization`.
 
 **Default:** ``ParserOptions { ... }``, where ``...`` depends on
-:ref:`config-commit_parser` as indicated above.
+:ref:`commit_parser <config-commit_parser>`.
 
 ----
 

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/pyproject.toml

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

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0/src/python_semantic_release.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: python-semantic-release
-Version: 9.16.1
+Version: 9.17.0
 Summary: Automatic Semantic Versioning for Python projects
 Author-email: Rolf Erik Lekang <me@rolflekang.com>
 License: MIT

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/__init__.py

@@ -24,7 +24,7 @@ from semantic_release.version import (
     tags_and_versions,
 )
 
-__version__ = "9.16.1"
+__version__ = "9.17.0"
 
 __all__ = [
     "CommitParser",

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/changelog/context.py

@@ -8,6 +8,8 @@ from pathlib import Path
 from re import compile as regexp
 from typing import TYPE_CHECKING, Any, Callable, Literal
 
+from semantic_release.helpers import sort_numerically
+
 if TYPE_CHECKING:  # pragma: no cover
     from jinja2 import Environment
 
@@ -87,6 +89,7 @@ def make_changelog_context(
             read_file,
             convert_md_to_rst,
             autofit_text_width,
+            sort_numerically,
         ),
     )
 

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/changelog/release_history.py

@@ -102,75 +102,85 @@ class ReleaseHistory:
 
                 released.setdefault(the_version, release)
 
-            # mypy will be happy if we make this an explicit string
-            commit_message = str(commit.message)
-
             log.info(
                 "parsing commit [%s] %s",
                 commit.hexsha[:8],
-                commit_message.replace("\n", " ")[:54],
-            )
-            parse_result = commit_parser.parse(commit)
-            commit_type = (
-                "unknown" if isinstance(parse_result, ParseError) else parse_result.type
-            )
-
-            has_exclusion_match = any(
-                pattern.match(commit_message) for pattern in exclude_commit_patterns
-            )
-
-            commit_level_bump = (
-                LevelBump.NO_RELEASE
-                if isinstance(parse_result, ParseError)
-                else parse_result.bump
+                str(commit.message).replace("\n", " ")[:54],
             )
+            # returns a ParseResult or list of ParseResult objects,
+            # it is usually one, but we split a commit if a squashed merge is detected
+            parse_results = commit_parser.parse(commit)
+            if not isinstance(parse_results, list):
+                parse_results = [parse_results]
+
+            is_squash_commit = bool(len(parse_results) > 1)
+
+            # iterate through parsed commits to add to changelog definition
+            for parsed_result in parse_results:
+                commit_message = str(parsed_result.commit.message)
+                commit_type = (
+                    "unknown"
+                    if isinstance(parsed_result, ParseError)
+                    else parsed_result.type
+                )
+                log.debug("commit has type '%s'", commit_type)
 
-            # Skip excluded commits except for any commit causing a version bump
-            # Reasoning: if a commit causes a version bump, and no other commits
-            # are included, then the changelog will be empty. Even if ther was other
-            # commits included, the true reason for a version bump would be missing.
-            if has_exclusion_match and commit_level_bump == LevelBump.NO_RELEASE:
-                log.info(
-                    "Excluding commit [%s] %s",
-                    commit.hexsha[:8],
-                    commit_message.replace("\n", " ")[:50],
+                has_exclusion_match = any(
+                    pattern.match(commit_message) for pattern in exclude_commit_patterns
                 )
-                continue
 
-            if (
-                isinstance(parse_result, ParsedCommit)
-                and not parse_result.include_in_changelog
-            ):
-                log.info(
-                    str.join(
-                        " ",
-                        [
-                            "Excluding commit %s (%s) because parser determined",
-                            "it should not included in the changelog",
-                        ],
-                    ),
-                    commit.hexsha[:8],
-                    commit_message.replace("\n", " ")[:20],
+                commit_level_bump = (
+                    LevelBump.NO_RELEASE
+                    if isinstance(parsed_result, ParseError)
+                    else parsed_result.bump
                 )
-                continue
 
-            if the_version is None:
+                # Skip excluded commits except for any commit causing a version bump
+                # Reasoning: if a commit causes a version bump, and no other commits
+                # are included, then the changelog will be empty. Even if ther was other
+                # commits included, the true reason for a version bump would be missing.
+                if has_exclusion_match and commit_level_bump == LevelBump.NO_RELEASE:
+                    log.info(
+                        "Excluding %s commit[%s] %s",
+                        "piece of squashed" if is_squash_commit else "",
+                        parsed_result.short_hash,
+                        commit_message.split("\n", maxsplit=1)[0][:20],
+                    )
+                    continue
+
+                if (
+                    isinstance(parsed_result, ParsedCommit)
+                    and not parsed_result.include_in_changelog
+                ):
+                    log.info(
+                        str.join(
+                            " ",
+                            [
+                                "Excluding commit[%s] because parser determined",
+                                "it should not included in the changelog",
+                            ],
+                        ),
+                        parsed_result.short_hash,
+                    )
+                    continue
+
+                if the_version is None:
+                    log.info(
+                        "[Unreleased] adding commit[%s] to unreleased '%s'",
+                        parsed_result.short_hash,
+                        commit_type,
+                    )
+                    unreleased[commit_type].append(parsed_result)
+                    continue
+
                 log.info(
-                    "[Unreleased] adding '%s' commit(%s) to list",
-                    commit.hexsha[:8],
+                    "[%s] adding commit[%s] to release '%s'",
+                    the_version,
+                    parsed_result.short_hash,
                     commit_type,
                 )
-                unreleased[commit_type].append(parse_result)
-                continue
-
-            log.info(
-                "[%s] adding '%s' commit(%s) to release",
-                the_version,
-                commit_type,
-                commit.hexsha[:8],
-            )
 
-            released[the_version]["elements"][commit_type].append(parse_result)
+                released[the_version]["elements"][commit_type].append(parsed_result)
 
         return cls(unreleased=unreleased, released=released)
 

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/changelog/template.py

@@ -54,7 +54,6 @@ def environment(
         autoescape_value = dynamic_import(autoescape)
     else:
         autoescape_value = autoescape
-    log.debug("%s", locals())
 
     return ComplexDirectorySandboxedEnvironment(
         block_start_string=block_start_string,

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/cli/changelog_writer.py

@@ -24,6 +24,7 @@ from semantic_release.cli.const import (
 )
 from semantic_release.cli.util import noop_report
 from semantic_release.errors import InternalError
+from semantic_release.helpers import sort_numerically
 
 if TYPE_CHECKING:  # pragma: no cover
     from jinja2 import Environment
@@ -254,7 +255,11 @@ def generate_release_notes(
         version=release["version"],
         release=release,
         mask_initial_release=mask_initial_release,
-        filters=(*hvcs_client.get_changelog_context_filters(), autofit_text_width),
+        filters=(
+            *hvcs_client.get_changelog_context_filters(),
+            autofit_text_width,
+            sort_numerically,
+        ),
     ).bind_to_environment(
         # Use a new, non-configurable environment for release notes -
         # not user-configurable at the moment

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/cli/commands/version.py

@@ -65,7 +65,7 @@ def is_forced_prerelease(
     log.debug(
         "%s: %s",
         is_forced_prerelease.__name__,
-        ", ".join(f"{k} = {v}" for k, v in local_vars),
+        str.join(", ", iter(f"{k} = {v}" for k, v in local_vars)),
     )
     return (
         as_prerelease

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/cli/config.py

@@ -602,7 +602,12 @@ class RuntimeContext:
         # Retrieve details from repository
         with Repo(str(raw.repo_dir)) as git_repo:
             try:
-                remote_url = raw.remote.url or git_repo.remote(raw.remote.name).url
+                # Get the remote url by calling out to `git remote get-url`. This returns
+                # the expanded url, taking into account any insteadOf directives
+                # in the git configuration.
+                remote_url = raw.remote.url or git_repo.git.remote(
+                    "get-url", raw.remote.name
+                )
                 active_branch = git_repo.active_branch.name
             except ValueError as err:
                 raise MissingGitRemote(

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/cli/masking_filter.py

@@ -27,7 +27,7 @@ class MaskingFilter(logging.Filter):
 
     def add_mask_for(self, data: str, name: str = "redacted") -> MaskingFilter:
         if data and data not in self._UNWANTED:
-            log.debug("Adding redact pattern %r to _redact_patterns", name)
+            log.debug("Adding redact pattern '%r' to redact_patterns", name)
             self._redact_patterns[name].add(data)
         return self
 

{python_semantic_release-9.16.1 → python_semantic_release-9.17.0}/src/semantic_release/commit_parser/_base.py

@@ -81,4 +81,4 @@ class CommitParser(ABC, Generic[_TT, _OPTS]):
         return self.parser_options()  # type: ignore[return-value]
 
     @abstractmethod
-    def parse(self, commit: Commit) -> _TT: ...
+    def parse(self, commit: Commit) -> _TT | list[_TT]: ...