Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update relekang/python-semantic-release action to v9 #65

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 6, 2024

This PR contains the following updates:

Package Type Update Change
relekang/python-semantic-release action major v8.7.2 -> v9.8.8

Release Notes

relekang/python-semantic-release (relekang/python-semantic-release)

v9.8.8

Compare Source

Documentation
  • docs(configuration): update build_command env table for windows to use all capital vars (0e8451c)

  • docs(github-actions): update version in examples to latest version (3c894ea)

Fix
  • fix(config): fix path traversal detection for windows compatibility (#​1014)

    The original implementation of the path traversal detection expected that resolve()
    works the same on windows as it does with Linux/Mac. Windows requires the folder paths
    to exist to be resolved and that is not the case when the template_dir is not being
    used.

    Resolves: #​994 (16e6daa)

v9.8.7

Compare Source

Documentation
  • docs: use pinned version for GHA examples (#​1004)

  • docs(github-actions): use pinned version for GHA examples

    Fixes #​1003

  • chore(scripts): add auto version bump to non dynamic docs text (i.e. code snippets)

  • docs(github-actions): adjust formatting & version warning in code snippets

  • style(docs-github-actions): adjust formatting for readability


Co-authored-by: codejedi365 <codejedi365@​gmail.com> (5fdf761)

  • docs(configuration): fix build_command_env table rendering (#​996) (a5eff0b)

  • docs(changelog): clarify description of the default changelog generation process (399fa65)

  • docs(configuration): clarify changelog_file vs template_dir option usage

Provided additional description that warns about the mutually-exclusive nature of
the changelog_file option and the template_dir option.

Resolves: #​983 (a7199c8)

Fix
  • fix: provide context.history global in release notes templates (#​1005)

  • fix(release-notes): provide context.history global in release note templates

    Temporarily return the context.history variable to release notes generation
    as many users are using it in their release documentation. It was never intended
    to be provided and will be removed in the future.

    context was removed in v9.8.3 during a refactor and condensing of changelog
    and release notes functionality.

    Resolves: #​984

  • fix(release-notes): fix noop-changelog to print raw release notes

    Some markdown sequences can be interpreted as ansi escape sequences which dilute
    debugging of release note templates by the user. This change ensures the raw
    content is displayed to the console as expected. (5bd91b4)

v9.8.6

Compare Source

Documentation
  • docs(configuration): correct GHA parameter name for commit email (#​981)

git_committer_name was repeated; replace one instance of it with
git_committer_email (ce9ffdb)

Fix
  • fix(version-cmd): resolve build command execution in powershell (#​980)

Fixes the command line option for passing a shell command to Powershell. Also included a similar shell detection result for
pwsh (Powershell Core) (32c8e70)

v9.8.5

Compare Source

Fix
  • fix: enable --print-last-released* when in detached head or non-release branch (#​926)

  • test(version-cmd): add tests to print when detached or non-release branch

    ref: #​900

  • fix(version-cmd): drop branch restriction for --print-last-released* opts

    Resolves: #​900 (782c0a6)

Performance
  • perf: improve git history processing for changelog generation (#​972)

  • perf(changelog): improve git history parser changelog generation

    This converts the double for-loop (O(n^2)) down to O(n) using a
    lookup table to match the current commit with a known tag rather than
    iterating through all the tags of the repository every time.

  • fix(changelog): resolve commit ordering issue when dates are similar (bfda159)

v9.8.4

Compare Source

Fix
  • fix(changelog-cmd): remove usage strings when error occured

Resolves: #​810 (348a51d)

  • fix(publish-cmd): remove usage strings when error occured

Resolves: #​810 (afbb187)

  • fix(config): prevent path traversal manipulation of target changelog location (43e35d0)

  • fix(version-cmd): remove usage strings when error occurred

Resolves: #​810 (a7c17c7)

  • fix(publish-cmd): prevent error when provided tag does not exist locally (16afbbb)

  • fix(config): prevent path traversal manipulation of target changelog location (3eb3dba)

  • fix(changelog-cmd): render default changelog when user template directory exist but is empty (bded8de)

v9.8.3

Compare Source

Fix
  • fix(parser): strip DOS carriage-returns in commits (#​956)

The default template can result in mixed (UNIX / DOS style) carriage
returns in the generated changelog. Use a string replace in the commit
parser to strip the DOS CRs ("\r"). This is only needed in the case when
we are not byte decoding.

Fixes #​955 (0b005df)

v9.8.2

Compare Source

Fix
  • fix(templates): suppress extra newlines in default changelog (#​954)

    Suppress extra newlines in default generated changelog output (7b0079b)

v9.8.1

Compare Source

Fix
  • fix: improve build cmd env on windows (#​942)

  • fix(version-cmd): pass windows specific env vars to build cmd when on windows

  • test(version-cmd): extend build cmd tests to include windows vars

  • docs(configuration): define windows specific env vars for build cmd

  • refactor(version-cmd): only add windows vars when windows is detected


Co-authored-by: Juan Cruz Mencia Naranjo <jcmencia@arsys.es> (d911fae)

v9.8.0

Compare Source

Documentation
  • docs(migration-v8): update version references in migration instructions (#​938) (d6ba16a)
Feature
  • feat: extend gitlab to edit a previous release if exists (#​934)

  • style(hvcs-github): update function docstrings for params

  • feat(hvcs-gitlab): enable gitlab to edit a previous release if found

  • fix(hvcs-gitlab): add tag message to release creation

  • fix(gitlab): adjust release name to mirror other hvcs release names

  • refactor(gitlab): consolidate & simplify usage of gitlab client

  • test(gitlab): neuter test cases that used the internet & add new tests

  • refactor(gitlab): handle errors in release retrieval gracefully

  • refactor(gitlab): update release notes editing implementation


Co-authored-by: bdorsey <brentadorsey@gmail.com> (23e02b9)

  • feat(gha): configure ssh signed tags in GitHub Action (#​937)

Resolves: #​936 (dfb76b9)

  • feat(version-cmd): add toggle of --no-verify option to git commit (#​927)

  • test(version-cmd): add test w/ failing pre-commit hook--preventing version commit

  • feat(version-cmd): add toggle of --no-verify option to git commit

    This commit adds a configuration option that toggles the addition of --no-verify
    command line switch on git commit operations that are run with the version command.

  • docs(configuration): add no_git_verify description to the configuration page


Co-authored-by: bdorsey <brentadorsey@gmail.com> (1de6f78)

v9.7.3

Compare Source

Fix
  • fix: enabled prelease-token parameter in github action (#​929) (1bb26b0)

v9.7.2

Compare Source

Documentation
  • docs(configuration): clarify TOC & alphabetize configuration descriptions (19add16)

  • docs(configuration): clarify TOC & standardize heading links (3a41995)

Fix
  • fix: enable user configuration of build_command env vars (#​925)
  • test(version): add test of user defined env variables in build command

    ref: #​922

  • fix(version): enable user config of build_command env variables

    Resolves: #​922

  • docs(configuration): document build_command_env configuration option (6b5b271)

v9.7.1

Compare Source

Fix

v9.7.0

Compare Source

Documentation
  • docs(configuration): add description of build command available env variables (c882dc6)
Feature
  • feat(version-cmd): pass NEW_VERSION & useful env vars to build command (ee6b246)
Fix

v9.6.0

Compare Source

Feature
  • feat: changelog filters are specialized per vcs type (#​890)

  • test(github): sync pr url expectation with GitHub api documentation

  • fix(github): correct changelog filter for pull request urls

  • refactor(hvcs-base): change to an abstract class & simplify interface

  • refactor(remote-hvcs-base): extend the base abstract class with common remote base class

  • refactor(github): adapt to new abstract base class

  • refactor(gitea): adapt to new abstract base class

  • refactor(gitlab): adapt to new abstract base class

  • refactor(bitbucket): adapt to new abstract base class

  • refactor(cmds): prevent hvcs from executing if not remote hosted vcs

  • feat(changelog): changelog filters are hvcs focused

  • test(hvcs): add validation for issue_url generation

  • feat(changelog-github): add issue url filter to changelog context

  • feat(changelog-gitea): add issue url filter to changelog context

  • refactor(cmd-version): consolidate asset uploads with release creation

  • style: resolve ruff errors

  • feat(changelog-context): add flag to jinja env for which hvcs is available

  • test(changelog-context): demonstrate per hvcs filters upon render

  • docs(changelog-context): explain new hvcs specific context filters

  • refactor(config): adjust default token resolution w/ subclasses (76ed593)

Fix
  • fix(parser-custom): gracefully handle custom parser import errors (67f6038)

  • fix: correct version --prerelease use & enable --as-prerelease (#​647)

  • test(version): add validation of --as-prerelease and --prerelease opts

  • fix(version-cmd): correct --prerelease use

    Prior to this change, --prerelease performed the role of converting whichever forced
    version into a prerelease version declaration, which was an unintentional breaking
    change to the CLI compared to v7.

    --prerelease now forces the next version to increment the prerelease revision,
    which makes it consistent with --patch, --minor and --major. Temporarily disabled
    the ability to force a prerelease.

    Resolves: #​639

  • feat(version-cmd): add --as-prerelease option to force the next version to be a prerelease

    Prior to this change, --prerelease performed the role that --as-prerelease now does,
    which was an unintentional breaking change to the CLI compared to v7.

    --prerelease is used to force the next version to increment the prerelease revision,
    which makes it consistent with --patch, --minor and --major, while --as-prerelease
    forces for the next version to be converted to a prerelease version type before it is
    applied to the project regardless of the bump level.

    Resolves: #​639

  • docs(commands): update version command options definition about prereleases


Co-authored-by: codejedi365 <codejedi365@​gmail.com> (2acb5ac)

v9.5.0

Compare Source

Build
Feature
  • feat: extend support to on-prem GitHub Enterprise Server (#​896)

  • test(github): adjust init test to match the Enterprise Server api url

  • feat(github): extend support to on-prem GitHub Enterprise Server

    Resolves: #​895 (4fcb737)

v9.4.2

Compare Source

Build
  • build(deps): update rich requirement from ~=12.5 to ~=13.0 (#​877)

Updates the requirements on rich to permit the latest version.

Resolves: #​888

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@​users.noreply.github.com> (4a22a8c)

Fix
  • fix(hvcs): allow insecure http connections if configured (#​886)

  • fix(gitlab): allow insecure http connections if configured

  • test(hvcs-gitlab): fix tests for clarity & insecure urls

  • test(conftest): refactor netrc generation into common fixture

  • refactor(hvcsbase): remove extrenous non-common functionality

  • fix(gitea): allow insecure http connections if configured

  • test(hvcs-gitea): fix tests for clarity & insecure urls

  • refactor(gitlab): adjust init function signature

  • fix(github): allow insecure http connections if configured

  • test(hvcs-github): fix tests for clarity & insecure urls

  • fix(bitbucket): allow insecure http connections if configured

  • test(hvcs-bitbucket): fix tests for clarity & insecure urls

  • fix(config): add flag to allow insecure connections

  • fix(version-cmd): handle HTTP exceptions more gracefully

  • style(hvcs): resolve typing issues & mimetype executions

  • test(cli-config): adapt default token test for env resolution

  • test(changelog-cmd): isolate env & correct the expected api url

  • test(fixtures): adapt repo builder for new hvcs init() signature

  • style: update syntax for 3.8 compatiblity & formatting

  • docs(configuration): update remote settings section with missing values

    Resolves: #​868

  • style(docs): improve configuration & api readability (db13438)

  • fix(hvcs): prevent double url schemes urls in changelog (#​676)

  • fix(hvcs): prevent double protocol scheme urls in changelogs

    Due to a typo and conditional stripping of the url scheme the
    hvcs_domain and hvcs_api_domain values would contain protocol schemes
    when a user specified one but the defaults would not. It would cause
    the api_url and remote_url to end up as "https://https://domain.com"

  • fix(bitbucket): correct url parsing & prevent double url schemes

  • fix(gitea): correct url parsing & prevent double url schemes

  • fix(github): correct url parsing & prevent double url schemes

  • fix(gitlab): correct url parsing & prevent double url schemes

  • test(hvcs): ensure api domains are derived correctly


Co-authored-by: codejedi365 <codejedi365@​gmail.com> (5cfdb24)

v9.4.1

Compare Source

Fix
  • fix(gh-actions-output): fixed trailing newline to match GITHUB_OUTPUT format (#​885)

  • test(gh-actions-output): fix unit tests to manage proper whitespace

    tests were adjusted for clarity and to replicate error detailed in #​884.

  • fix(gh-actions-output): fixed trailing newline to match GITHUB_OUTPUT format

    Resolves: #​884 (2c7b6ec)

v9.4.0

Compare Source

Feature
  • feat(gitea): derives gitea api domain from base domain when unspecified (#​675)

  • test(gitea): add test of custom server path & custom api domain

  • feat(gitea): derives gitea api domain from base domain when unspecified

  • refactor(hvcs-gitea): uniformly handle protocol prefixes


Co-authored-by: codejedi365 <codejedi365@​gmail.com> (2ee3f8a)

v9.3.1

Compare Source

Fix
  • fix(cli-version): change implementation to only push the tag we generated

Restricts the git push command to only push the explicit tag we created
which will eliminate the possibility of pushing another tag that could
cause an error.

Resolves: #​803 (8a9da4f)

  • fix(algorithm): handle merge-base errors gracefully

Merge-base errors generally occur from a shallow clone that is
primarily used by CI environments and will cause PSR to explode
prior to this change. Now it exits with an appropriate error.

Resolves: #​724 (4c998b7)

Performance
  • perf(algorithm): simplify logs & use lookup when searching for commit & tag match (3690b95)

v9.3.0

Compare Source

Feature
  • feat(cmd-version): changelog available to bundle (#​779)

  • test(util): fix overlooked file differences in folder comparison

  • test(version): tracked changelog as changed file on version create

Removes the temporary release_notes hack to prevent CHANGELOG generation on
execution of version command. Now that it is implemented we can remove the
fixture to properly pass the tests.

  • feat(cmd-version): create changelog prior to build enabling doc bundling (37fdb28)

v9.2.2

Compare Source

Fix
  • fix(cli): enable subcommand help even if config is invalid

Refactors configuration loading to use lazy loading by subcommands
triggered by the property access of the runtime_ctx object. Resolves
the issues when running --help on subcommands when a configuration
is invalid

Resolves: #​840 (91d221a)

v9.2.1

Compare Source

Fix
  • fix(parse-git-url): handle urls with url-safe special characters (27cd93a)

v9.2.0

Compare Source

Build
  • build(deps): add click-option-group for grouping exclusive flags (bd892b8)
Documentation
  • docs(configuration): clarify the major_on_zero configuration option (f7753cd)

  • docs(configuration): add description of allow-zero-version configuration option (4028f83)

Feature
  • feat(version-config): add option to disable 0.x.x versions (dedb3b7)

  • feat(version): add new version print flags to display the last released version and tag (814240c)

Fix
  • fix(changelog-generation): fix incorrect release timezone determination (f802446)

  • fix(changelog): make sure default templates render ending in 1 newline (0b4a45e)

v9.1.1

Compare Source

Fix
  • fix(parse_git_url): fix bad url with dash (1c25b8e)

v9.1.0

Compare Source

Build
  • build(deps): bump minimum required tomlkit to &gt;=0.11.0

TOMLDocument is missing the unwrap() function in v0.10.2 which
causes an AttributeError to occur when attempting to read a the text
in pyproject.toml as discovered with #​834

Resolves: #​834 (291aace)

Documentation
  • docs: add bitbucket to token table (56f146d)

  • docs: add bitbucket authentication (b78a387)

  • docs: fix typo (b240e12)

Feature
  • feat: add bitbucket hvcs (bbbbfeb)
Fix
  • fix: remove unofficial environment variables (a5168e4)

v9.0.3

Compare Source

Fix
  • fix(algorithm): correct bfs to not abort on previously visited node (02df305)
Performance
  • perf(algorithm): refactor bfs search to use queue rather than recursion (8b742d3)

v9.0.2

Compare Source

Documentation
  • docs: Remove duplicate note in configuration.rst (#​807) (fb6f243)
Fix
  • fix(util): properly parse windows line-endings in commit messages

Due to windows line-endings \r\n, it would improperly split the commit
description (it failed to split at all) and cause detection of Breaking changes
to fail. The breaking changes regular expression looks to the start of the line
for the proper syntax.

Resolves: #​820 (70193ba)

v9.0.1

Compare Source

Fix
  • fix(config): set commit parser opt defaults based on parser choice (#​782) (9c594fb)

v9.0.0

Compare Source

Breaking

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 6, 2024
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 36c0cda to fa8d459 Compare February 8, 2024 09:02
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from fa8d459 to 153cc0b Compare February 8, 2024 12:14
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 153cc0b to da69f14 Compare February 14, 2024 22:13
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from da69f14 to c3911d5 Compare February 25, 2024 10:21
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from c3911d5 to d4e1c62 Compare March 18, 2024 15:25
Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.73%. Comparing base (e9cc18e) to head (94dd034).

Current head 94dd034 differs from pull request most recent head 7893c3b

Please upload reports for the commit 7893c3b to get more accurate results.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #65   +/-   ##
=======================================
  Coverage   79.73%   79.73%           
=======================================
  Files           4        4           
  Lines         153      153           
  Branches       29       29           
=======================================
  Hits          122      122           
  Misses         31       31           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from d4e1c62 to 6cad779 Compare March 19, 2024 07:36
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 6cad779 to afa296a Compare March 21, 2024 08:03
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from afa296a to fca5407 Compare March 24, 2024 08:08
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from fca5407 to f19cff8 Compare March 31, 2024 21:19
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from f19cff8 to 94dd034 Compare April 6, 2024 22:20
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 94dd034 to 72d564a Compare April 14, 2024 05:18
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 72d564a to 56a00eb Compare April 23, 2024 04:46
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 56a00eb to 73597e1 Compare April 29, 2024 08:35
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 73597e1 to db3af64 Compare May 6, 2024 10:52
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from db3af64 to c2fa8d1 Compare May 7, 2024 04:04
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from c2fa8d1 to 5c7239d Compare May 13, 2024 05:00
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 5c7239d to 8246f2b Compare May 15, 2024 11:58
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 8246f2b to e65634c Compare May 27, 2024 17:00
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from e65634c to 3aea097 Compare June 5, 2024 01:13
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 3aea097 to ea56279 Compare June 17, 2024 06:25
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from ea56279 to 7893c3b Compare June 18, 2024 06:27
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 7893c3b to 3c2d882 Compare July 4, 2024 18:56
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 3c2d882 to 155b8ec Compare July 7, 2024 00:54
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 155b8ec to 19ea4c3 Compare July 20, 2024 12:59
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 19ea4c3 to eadad10 Compare August 20, 2024 08:19
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from eadad10 to 31afc75 Compare September 1, 2024 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants