python-semantic-release 9.19.0__tar.gz → 9.19.1__tar.gz

{python_semantic_release-9.19.0/src/python_semantic_release.egg-info → python_semantic_release-9.19.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: python-semantic-release
-Version: 9.19.0
+Version: 9.19.1
 Summary: Automatic Semantic Versioning for Python projects
 Author-email: Rolf Erik Lekang <me@rolflekang.com>
 License: MIT
@@ -62,7 +62,7 @@ Requires-Dist: pre-commit~=3.5; extra == "dev"
 Requires-Dist: tox~=4.11; extra == "dev"
 Requires-Dist: ruff==0.6.1; extra == "dev"
 Provides-Extra: mypy
-Requires-Dist: mypy==1.14.1; extra == "mypy"
+Requires-Dist: mypy==1.15.0; extra == "mypy"
 Requires-Dist: types-requests~=2.32.0; extra == "mypy"
 Requires-Dist: types-pyyaml~=6.0; extra == "mypy"
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/algorithm.rst

@@ -35,7 +35,7 @@ Implementation
 
 1. Parse all the Git tags of the repository into semantic versions, and **sort**
    in descending (most recent first) order according to `semver precedence`_.
-   Ignore any tags which do not correspond to valid semantic vesrions according
+   Ignore any tags which do not correspond to valid semantic versions according
    to ``tag_format``.
 
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.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.18.1
+    - uses: python-semantic-release/python-semantic-release@v9.19.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.18.1
+    - uses: python-semantic-release/publish-action@v9.19.0
       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.18.1
+            uses: python-semantic-release/python-semantic-release@v9.19.0
             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.18.1
+            uses: python-semantic-release/publish-action@v9.19.0
             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.18.1
+    uses: python-semantic-release/python-semantic-release@v9.19.0
     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.18.1
+     uses: python-semantic-release/python-semantic-release@v9.19.0
      with:
        directory: ./project1
        github_token: ${{ secrets.GITHUB_TOKEN }}
 
    - name: Release Project 2
-     uses: python-semantic-release/python-semantic-release@v9.18.1
+     uses: python-semantic-release/python-semantic-release@v9.19.0
      with:
        directory: ./project2
        github_token: ${{ secrets.GITHUB_TOKEN }}

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/automatic-releases/index.rst

@@ -13,6 +13,8 @@ Guides
 ^^^^^^
 
 .. toctree::
+    :maxdepth: 2
+
     travis
     github-actions
     cronjobs

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/changelog_templates.rst

@@ -49,7 +49,7 @@ PSR provides two default changelog output formats:
 Both formats are kept in sync with one another to display the equivalent information
 in the respective format. The default changelog template is located in the
 ``data/templates/`` directory within the PSR package. The templates are written in
-modular style (ie. multiple files) and during the render proccess are ultimately
+modular style (ie. multiple files) and during the render process are ultimately
 combined together to render the final changelog output. The rendering start point
 is the ``CHANGELOG.{FORMAT_EXT}.j2`` underneath the respective format directory.
 
@@ -144,7 +144,7 @@ newly created changelog file.
 
 .. tip::
     We have accomplished changelog updating through the use of the `Jinja`_ templating
-    and addtional context filters and context variables. This is notable because
+    and additional context filters and context variables. This is notable because
     in the case that you want to customize your changelog template, you now can use the
     same logic to enable changelog updates of your custom template!
 
@@ -1220,7 +1220,7 @@ __ https://github.com/python-semantic-release/python-semantic-release/tree/maste
     maintain any content that should be included before the new release information.
     See ``data/templates/*/md/.components/changelog_update.md.j2`` for reference.
 
-5.  **Print your insertion flag.** This is impartive to ensure that the resulting
+5.  **Print your insertion flag.** This is imperative to ensure that the resulting
     changelog can be updated in the future. See
     ``data/templates/*/md/.components/changelog_update.md.j2`` for reference.
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/commands.rst

@@ -272,8 +272,8 @@ the flag.
 This can be useful when making a single prerelease on a branch that would typically release
 normal versions.
 
-If not specified in :ref:`cmd-version-option-prerelease-token`, the prerelease token is idenitified using the
-:ref:`Multibranch Release Configuration <multibranch-releases-configuring>`
+If not specified in :ref:`cmd-version-option-prerelease-token`, the prerelease token is identified
+using the :ref:`Multibranch Release Configuration <multibranch-releases-configuring>`
 
 See the examples alongside :ref:`cmd-version-option-force-level` for how to use this flag.
 
@@ -282,8 +282,9 @@ See the examples alongside :ref:`cmd-version-option-force-level` for how to use
 ``--prerelease-token [VALUE]``
 ******************************
 
-Force the next version to use the value as the prerelease token. This overrides the configured value if one is
-present. If not used during a release producing a prerelease version, this option has no effect.
+Force the next version to use the value as the prerelease token. This overrides the configured
+value if one is present. If not used during a release producing a prerelease version, this
+option has no effect.
 
 .. _cmd-version-option-build-metadata:
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/commit_parsing.rst

@@ -49,7 +49,7 @@ Built-in Commit Parsers
 The following parsers are built in to Python Semantic Release:
 
 - :ref:`ConventionalCommitParser <commit_parser-builtin-conventional>`
-- :ref:`AngularCommitParser <commit_parser-builtin-angular>` *(deprecated in ${NEW_RELEASE_TAG})*
+- :ref:`AngularCommitParser <commit_parser-builtin-angular>` *(deprecated in v9.19.0)*
 - :ref:`EmojiCommitParser <commit_parser-builtin-emoji>`
 - :ref:`ScipyCommitParser <commit_parser-builtin-scipy>`
 - :ref:`TagCommitParser <commit_parser-builtin-tag>` *(deprecated in v9.12.0)*
@@ -61,7 +61,7 @@ The following parsers are built in to Python Semantic Release:
 Conventional Commits Parser
 """""""""""""""""""""""""""
 
-*Introduced in ${NEW_RELEASE_TAG}*
+*Introduced in v9.19.0*
 
 A parser that is designed to parse commits formatted according to the
 `Conventional Commits Specification`_.  The parser is implemented with the following
@@ -140,7 +140,7 @@ Angular Commit Parser
 """""""""""""""""""""
 
 .. warning::
-  This parser was deprecated in ``${NEW_RELEASE_TAG}``. It will be removed in a future release.
+  This parser was deprecated in ``v9.19.0``. It will be removed in a future release.
   This parser is being replaced by the :ref:`commit_parser-builtin-conventional`.
 
 A parser that is designed to parse commits formatted according to the
@@ -423,7 +423,7 @@ a ``release_notices`` attribute that is a tuple of string paragraphs to identify
 release notice.
 
 In the default changelog and release notes template, these release notices will be
-formatted into their own section called **ADDITIONAL RELEASE INFORMATION**. Each will
+formatted into their own section called **Additional Release Information**. Each will
 include any commit scope defined and each release notice in alphabetical order.
 
 ----

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/configuration.rst

@@ -88,9 +88,12 @@ environment variable is:
     default = "default value"
 
 In this structure:
+
   * ``env`` represents the environment variable that Python Semantic Release will search for
+
   * ``default_env`` is a fallback environment variable to read in case the variable specified
     by ``env`` is not set. This is optional - if not specified then no fallback will be used.
+
   * ``default`` is a default value to use in case the environment variable specified by ``env``
     is not set. This is optional - if ``default`` is not specified then the environment variable
     specified by ``env`` is considered required.
@@ -105,7 +108,7 @@ configuration setting. If there are type mis-matches, PSR will throw validation
 If a setting is not provided, than PSR will fill in the value with the default value.
 
 Python Semantic Release expects a root level key to start the configuration definition. Make
-sure to use the correct root key dependending on the configuration format you are using.
+sure to use the correct root key depending on the configuration format you are using.
 
 .. note:: If you are using ``pyproject.toml``, this heading should include the ``tool`` prefix
           as specified within PEP 517, resulting in ``[tool.semantic_release]``.
@@ -405,7 +408,7 @@ This setting is used to specify the output format the default changelog template
 will use when rendering the changelog. PSR supports both Markdown (``md``) and
 reStructuredText (``rst``) formats.
 
-This setting will take presendence over the file extension of the
+This setting will take precedence over the file extension of the
 :ref:`config-changelog-default_templates-changelog_file` setting. If this setting is
 omitted, the file extension of the :ref:`config-changelog-default_templates-changelog_file`
 setting will be used to determine the output format. If the file extension is not recognized,
@@ -695,10 +698,6 @@ A string that will be used to identify where the new version should be inserted
 changelog file (as defined by :ref:`config-changelog-changelog_file`) when the changelog mode
 is set to ``update``.
 
-When the changelog mode is set to ``init``, this string will be included as part of the
-header of the changelog file to initialize the changelog with a format that will be condusive
-for future version insertions.
-
 If you modify this value in your config, you will need to manually update any saved changelog
 file to match the new insertion flag if you use the ``update`` mode.  In ``init`` mode, the
 changelog file will be overwritten as normal.
@@ -790,8 +789,8 @@ Specify which commit parser Python Semantic Release should use to parse the comm
 within the Git repository.
 
 Built-in parsers:
-    * ``angular`` - :ref:`AngularCommitParser <commit_parser-builtin-angular>` *(deprecated in ${NEW_RELEASE_TAG})*
-    * ``conventional`` - :ref:`ConventionalCommitParser <commit_parser-builtin-conventional>` *(available in ${NEW_RELEASE_TAG}+)*
+    * ``angular`` - :ref:`AngularCommitParser <commit_parser-builtin-angular>` *(deprecated in v9.19.0)*
+    * ``conventional`` - :ref:`ConventionalCommitParser <commit_parser-builtin-conventional>` *(available in v9.19.0+)*
     * ``emoji`` - :ref:`EmojiCommitParser <commit_parser-builtin-emoji>`
     * ``scipy`` - :ref:`ScipyCommitParser <commit_parser-builtin-scipy>`
     * ``tag`` - :ref:`TagCommitParser <commit_parser-builtin-tag>` *(deprecated in v9.12.0)*
@@ -965,7 +964,7 @@ calls rather than the primary domain (ex. ``api.github.com``).
 
 **Most on-premise HVCS installations will NOT use this setting!** Whether or not
 this value is used depends on the HVCS configured (and your server administration)
-in the :ref:`remote.type <config-remote-type>` setting and used in tadem with the
+in the :ref:`remote.type <config-remote-type>` setting and used in tandem with the
 :ref:`remote.domain <config-remote-domain>` setting.
 
 When using a custom :ref:`remote.domain <config-remote-domain>` and a HVCS
@@ -1058,7 +1057,7 @@ used for the connection. If the protocol scheme is provided in the field value,
 match this setting or it will throw an error.
 
 The purpose of this flag is to prevent any typos in provided ``domain`` and ``api_domain``
-values that accidently specify an insecure connection but allow users to toggle the protection
+values that accidentally specify an insecure connection but allow users to toggle the protection
 scheme off when desired.
 
 **Default:** ``false``

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/index.rst

@@ -219,7 +219,7 @@ and changelogs. The user has three options to push changes to the repository:
    - :ref:`Changelog <config-changelog>` - customize your project's changelog.
    - :ref:`changelog-templates-custom_release_notes` - customize the published release notes
    - :ref:`upload_to_vcs_release <config-publish-upload_to_vcs_release>` -
-     enable/disable uploading artefacts to VCS releases
+     enable/disable uploading artifacts to VCS releases
    - :ref:`version --vcs-release/--no-vcs-release <cmd-version-option-vcs-release>` - enable/disable VCS release
      creation.
    - `upload-to-gh-release`_, a GitHub Action for running ``semantic-release publish``

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/multibranch_releases.rst

@@ -45,12 +45,12 @@ a situation may occur in the following scenario:
 Suppose that Python Semantic Release has been configured to use the same
 prerelease token ``"alpha"`` for all ``feature-*`` branches, and the default tag
 format ``"v{version}"``. In this case, running a pre-release from branch ``feature-1``
-will recognise that since the last release, ``1.1.0``, a **feature** has been
+will recognize that since the last release, ``1.1.0``, a **feature** has been
 introduced and therefore the next tag to be applied to ``feature-1`` will be
 ``v1.2.0-alpha.1``.
 
 However, suppose we then try to run a release against ``feature-2``. This will also
-recognise that a **feature** has been introduced against the last released version of
+recognize that a **feature** has been introduced against the last released version of
 ``v1.1.0`` and therefore will try to create the tag ``v1.2.0-alpha.1``, leading to an
 error as this tag was already created against ``feature-1``.
 
@@ -91,7 +91,7 @@ Each release group is configured as a nested mapping under the
 ``tool.semantic_release.branches`` key in ``pyproject.toml``, or the equivalent
 structure in other formats. the mapping requires a single key that is used as a
 name for the release group, which can help to identify it in log messages but has
-no effect on the behaviour of the release. For example, Python Semantic Release has
+no effect on the behavior of the release. For example, Python Semantic Release has
 only one release group by default with the name ``main``.
 
 Inside each release group, the following key-value pairs can be set:

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/strict_mode.rst

@@ -4,7 +4,7 @@ Strict Mode
 ===========
 
 Strict Mode is enabled by use of the :ref:`strict <cmd-main-option-strict>` parameter
-to the main command for Python Semantic Release. Strict Mode alters the behaviour of
+to the main command for Python Semantic Release. Strict Mode alters the behavior of
 Python Semantic Release when certain conditions are encountered that prevent Python
 Semantic Release from performing an action. Typically, this will result in a warning
 becoming an error, or a different exit code (0 vs non-zero) being produced when Python

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/docs/troubleshooting.rst

@@ -10,7 +10,8 @@ Troubleshooting
 .. _troubleshooting-verbosity:
 
 Increasing Verbosity
-====================
+--------------------
+
 If you are having trouble with Python Semantic Release or would like to see additional
 information about the actions that it is taking, you can use the top-level
 :ref:`cmd-main-option-verbosity` option. This can be supplied multiple times to increase
@@ -24,12 +25,10 @@ For example::
 
     semantic-release -vv version --print
 
-
 .. note::
    The :ref:`cmd-main-option-verbosity` option must be supplied to the top-level
    ``semantic-release`` command, before the name of any sub-command.
 
-
 .. warning::
    The volume of logs when using ``DEBUG`` verbosity may be significantly increased,
    compared to ``INFO`` or the default ``WARNING``, and as a result executing commands

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-semantic-release"
-version = "9.19.0"
+version = "9.19.1"
 description = "Automatic Semantic Versioning for Python projects"
 requires-python = ">=3.8"
 license = { text = "MIT" }
@@ -82,7 +82,7 @@ dev = [
   "ruff == 0.6.1"
 ]
 mypy = [
-  "mypy == 1.14.1",
+  "mypy == 1.15.0",
   "types-requests ~= 2.32.0",
   "types-pyyaml ~= 6.0",
 ]
@@ -398,7 +398,7 @@ ignore_names = ["change_to_ex_proj_dir", "init_example_project"]
 
 [tool.semantic_release]
 logging_use_named_masks = true
-commit_parser = "angular"
+commit_parser = "conventional"
 commit_parser_options = { parse_squash_commits = true, ignore_merge_commits = true }
 build_command = """
     python -m pip install -e .[build]

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1/src/python_semantic_release.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: python-semantic-release
-Version: 9.19.0
+Version: 9.19.1
 Summary: Automatic Semantic Versioning for Python projects
 Author-email: Rolf Erik Lekang <me@rolflekang.com>
 License: MIT
@@ -62,7 +62,7 @@ Requires-Dist: pre-commit~=3.5; extra == "dev"
 Requires-Dist: tox~=4.11; extra == "dev"
 Requires-Dist: ruff==0.6.1; extra == "dev"
 Provides-Extra: mypy
-Requires-Dist: mypy==1.14.1; extra == "mypy"
+Requires-Dist: mypy==1.15.0; extra == "mypy"
 Requires-Dist: types-requests~=2.32.0; extra == "mypy"
 Requires-Dist: types-pyyaml~=6.0; extra == "mypy"
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/python_semantic_release.egg-info/requires.txt

@@ -26,7 +26,7 @@ sphinx-autobuild==2024.2.4
 furo~=2024.1
 
 [mypy]
-mypy==1.14.1
+mypy==1.15.0
 types-requests~=2.32.0
 types-pyyaml~=6.0
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/__init__.py

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

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/__main__.py

@@ -8,6 +8,7 @@ from traceback import format_exception
 
 from semantic_release import globals
 from semantic_release.cli.commands.main import main as cli_main
+from semantic_release.enums import SemanticReleaseLogLevels
 
 
 def main() -> None:
@@ -18,7 +19,7 @@ def main() -> None:
         print("\n-- User Abort! --", file=sys.stderr)
         sys.exit(127)
     except Exception as err:  # noqa: BLE001, graceful error handling across application
-        if globals.debug:
+        if globals.log_level <= SemanticReleaseLogLevels.DEBUG:
             print(f"{err.__class__.__name__}: {err}\n", file=sys.stderr)
             etype, value, traceback = sys.exc_info()
             print(
@@ -35,9 +36,12 @@ def main() -> None:
                 file=sys.stderr,
             )
 
-        print(f"::ERROR:: {err}", file=sys.stderr)
+        print(
+            str.join("\n", [f"::ERROR:: {line}" for line in str(err).splitlines()]),
+            file=sys.stderr,
+        )
 
-        if not globals.debug:
+        if globals.log_level > SemanticReleaseLogLevels.DEBUG:
             print(
                 "Run semantic-release in very verbose mode (-vv) to see the full traceback.",
                 file=sys.stderr,

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/cli/commands/main.py

@@ -116,10 +116,10 @@ def main(
         SemanticReleaseLogLevels.SILLY,
     ]
 
-    log_level = log_levels[verbosity]
+    globals.log_level = log_levels[verbosity]
 
     logging.basicConfig(
-        level=log_level,
+        level=globals.log_level,
         format=FORMAT,
         datefmt="[%X]",
         handlers=[
@@ -130,10 +130,7 @@ def main(
     )
 
     logger = logging.getLogger(__name__)
-    logger.debug("logging level set to: %s", logging.getLevelName(log_level))
-
-    if log_level <= logging.DEBUG:
-        globals.debug = True
+    logger.debug("logging level set to: %s", logging.getLevelName(globals.log_level))
 
     if noop:
         rprint(

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/cli/config.py

@@ -665,6 +665,17 @@ class RuntimeContext:
                 if raw.commit_parser in _known_commit_parsers
                 else dynamic_import(raw.commit_parser)
             )
+        except ValueError as err:
+            raise ParserLoadError(
+                str.join(
+                    "\n",
+                    [
+                        f"Unrecognized commit parser value: {raw.commit_parser!r}.",
+                        str(err),
+                        "Unable to load the given parser! Check your configuration!",
+                    ],
+                )
+            ) from err
         except ModuleNotFoundError as err:
             raise ParserLoadError(
                 str.join(

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/data/templates/angular/md/.components/changes.md.j2

@@ -18,7 +18,7 @@ EXAMPLE:
 - Fix bug ([#11](https://domain.com/namespace/repo/pull/11),
   [`abcdef1`](https://domain.com/namespace/repo/commit/HASH))
 
-### BREAKING CHANGES
+### Breaking Changes
 
 - With the change _____, the change causes ___ effect. Ultimately, this section
   it is a more detailed description of the breaking change. With an optional
@@ -27,7 +27,7 @@ EXAMPLE:
 - **scope**: this breaking change has a scope to identify the part of the code that
   this breaking change applies to for better context.
 
-### ADDITIONAL RELEASE INFORMATION
+### Additional Release Information
 
 - This is a release note that provides additional information about the release
   that is not a breaking change or a feature/bug fix.
@@ -96,7 +96,7 @@ EXAMPLE:
 %}{#
    #    # PRINT BREAKING CHANGE DESCRIPTIONS (header & descriptions)
 #}{{    "\n"
-}}{{    "### BREAKING CHANGES\n"
+}}{{    "### Breaking Changes\n"
 }}{{
         "\n%s\n" | format(brking_descriptions | unique | join("\n\n"))
 }}{#
@@ -129,7 +129,7 @@ EXAMPLE:
 %}{#
    #    # PRINT RELEASE NOTICE INFORMATION (header & descriptions)
 #}{{    "\n"
-}}{{    "### ADDITIONAL RELEASE INFORMATION\n"
+}}{{    "### Additional Release Information\n"
 }}{{
         "\n%s\n" | format(release_notices | unique | join("\n\n"))
 }}{#

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/data/templates/angular/md/.release_notes.md.j2

@@ -14,13 +14,13 @@ _This release is published under the MIT License._
 
 - Fix bug (#11, [`abcdef1`](https://domain.com/namespace/repo/commit/HASH))
 
-### BREAKING CHANGES
+### Breaking Changes
 
 - With the change _____, the change causes ___ effect. Ultimately, this section it is a more detailed description of the breaking change. With an optional scope prefix like the commit messages above.
 
 - **scope**: this breaking change has a scope to identify the part of the code that this breaking change applies to for better context.
 
-### ADDITIONAL RELEASE INFORMATION
+### Additional Release Information
 
 - This is a release note that provides additional information about the release that is not a breaking change or a feature/bug fix.
 

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/data/templates/angular/rst/.components/changes.rst.j2

@@ -18,7 +18,7 @@ Bug Fixes
 
 * Fix bug (`#11`_, `8a7b8ec`_)
 
-BREAKING CHANGES
+Breaking Changes
 ----------------
 
 * With the change _____, the change causes ___ effect. Ultimately, this section
@@ -28,7 +28,7 @@ BREAKING CHANGES
 * **scope**: this breaking change has a scope to identify the part of the code that
   this breaking change applies to for better context.
 
-ADDITIONAL RELEASE INFORMATION
+Additional Release Information
 ------------------------------
 
 * This is a release note that provides additional information about the release
@@ -124,7 +124,7 @@ ADDITIONAL RELEASE INFORMATION
 %}{#
    #    # PRINT BREAKING CHANGE DESCRIPTIONS (header & descriptions)
 #}{{    "\n"
-}}{{    "BREAKING CHANGES\n"
+}}{{    "Breaking Changes\n"
 }}{{    '----------------\n'
 }}{{
         "\n%s\n" | format(brking_descriptions | unique | join("\n\n"))
@@ -158,7 +158,7 @@ ADDITIONAL RELEASE INFORMATION
 %}{#
    #    # PRINT RELEASE NOTICE INFORMATION (header & descriptions)
 #}{{    "\n"
-}}{{    "ADDITIONAL RELEASE INFORMATION\n"
+}}{{    "Additional Release Information\n"
 }}{{    "------------------------------\n"
 }}{{
         "\n%s\n" | format(release_notices | unique | join("\n\n"))

python_semantic_release-9.19.1/src/semantic_release/globals.py

@@ -0,0 +1,8 @@
+"""Semantic Release Global Variables."""
+
+from __future__ import annotations
+
+from semantic_release.enums import SemanticReleaseLogLevels
+
+log_level: SemanticReleaseLogLevels = SemanticReleaseLogLevels.WARNING
+"""int: Logging level for semantic-release"""

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/src/semantic_release/helpers.py

@@ -157,6 +157,12 @@ def dynamic_import(import_path: str) -> Any:
     Dynamically import an object from a conventionally formatted "module:attribute"
     string
     """
+    if ":" not in import_path:
+        raise ValueError(
+            f"Invalid import path {import_path!r}, must use 'module:Class' format"
+        )
+
+    # Split the import path into module and attribute
     module_name, attr = import_path.split(":", maxsplit=1)
 
     # Check if the module is a file path, if it can be resolved and exists on disk then import as a file

{python_semantic_release-9.19.0 → python_semantic_release-9.19.1}/tests/fixtures/git_repo.py

@@ -1689,7 +1689,7 @@ def simulate_default_changelog_creation(  # noqa: C901
 
         # Add breaking changes to the end of the version entry
         if brking_descriptions:
-            version_entry.append("### BREAKING CHANGES\n")
+            version_entry.append("### Breaking Changes\n")
             version_entry.extend([*sorted(brking_descriptions), ""])
 
         return str.join("\n", version_entry)
@@ -1822,7 +1822,7 @@ def simulate_default_changelog_creation(  # noqa: C901
 
         # Add breaking changes to the end of the version entry
         if brking_descriptions:
-            version_entry.append("BREAKING CHANGES")
+            version_entry.append("Breaking Changes")
             version_entry.append("-" * len(version_entry[-1]) + "\n")
             version_entry.extend([*sorted(brking_descriptions), ""])
 
@@ -2067,7 +2067,7 @@ def generate_default_release_notes_from_def(  # noqa: C901
 
         # Add breaking changes to the end of the version entry
         if brking_descriptions:
-            version_entry.append("### BREAKING CHANGES\n")
+            version_entry.append("### Breaking Changes\n")
             version_entry.extend([*sorted(brking_descriptions), ""])
 
         return str.join("\n", version_entry)