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 #1084

Open
wants to merge 2 commits 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 v7.34.6 -> v9.11.0

Release Notes

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

v9.11.0

Compare Source

Features
  • feat(changelog): add default changelog template in reStructuredText format (#​1055)

  • test(fixtures): update repo generation to create rst & md changelogs

  • test(release-history): refactor fragile test to utilize repo fixture definitions

  • test(changelog-cmd): update tests to evaluate rst changelog generation & updates

  • test(version-cmd): update tests to evaluate rst changelog generation & updates

  • test(version-cmd): update test code to match new commit definition functions

  • test(config): add test to validate insertion_flag default determination

  • feat(changelog): add convert_md_to_rst filter to changelog environment

  • feat(changelog): add default changelog in re-structured text format

    This change adds the templates to create an equivalent CHANGELOG.RST file in
    angular changelog style. It can be enabled via the output_format configuration
    setting.

    Resolves: #​399

  • feat(config): enable target changelog filename to trigger RST output format

    Resolves: #​399

  • feat(config): enable default changelog.insertion_flag based on output format

  • refactor(config): move changelog_file setting under changelog.default_templates

    This change adds a secondary changelog_file setting under the default_templates
    section while deprecating the top level one. Since this is not intended to be a
    breaking change we provided a warning message and compatibility code to pass along
    the current changelog_file value to the new setting location while giving the user
    a notification to update before the next version.

  • fix(changelog): correct spacing for default markdown template during updates

  • docs(configuration): update details of insertion_flag's dynamic defaults with rst

  • docs(configuration): update output_format description for reStructuredText support

  • docs(configuration): update changelog_file with deprecation notice of setting relocation

  • docs(changelog): clarify the convert_md_to_rst filter added to the template environment

  • docs(changelog): increase detail about configuration options of default changelog creation (c2e8831)

v9.10.1

Compare Source

Fixes
  • fix(config): handle branch match regex errors gracefully (#​1054)

prevents stacktrace error when user provided regex for a branch name match
is invalid. Translates most common failure of a plain wildcard * character to
the implied proper regex (4d12251)

v9.10.0

Compare Source

Documentation
  • docs(github-actions): update primary example with workflow sha controlled pipeline (14f04df)
Features
  • feat(changelog): modify changelog template to support changelog updates (#​1045)

  • feat(changelog): add read_file function to changelog template context

    This feature adds a filter that will enable jinja templates to read a file
    from the repository into memory to then use as output within the template.
    The primary use for this is to read in a previous changelog file which then
    the template can give the illusion of insertion as it re-writes the entire
    file.

  • feat(changelog): add changelog_mode to changelog template context

    Adds a flag that can be passed to the templating environment to allow
    for triggering an update mode of a changelog versions an initialization
    mode. The usage is up to the template developer but for PSR it is used
    to handle changelog generation vs changelog updating.

  • feat(changelog): add prev_changelog_file to changelog template context

    This adds a string that represents a filename to a previous changelog file
    which can be read from inside the template context. The primary use is for
    enabling the updating of a changelog through jinja templating.

  • feat(changelog): add changelog_insertion_flag to changelog template context

    This adds a customizable string to the jinja templating context which allows users
    to use the PSR configuration to pass a custom insertion flag into the templating
    context. This is intended for use with initializing a changelog and then updating
    it from that point forward.

  • feat(changelog): add shorthand ctx variable to changelog template env

  • refactor(changelog): change recursive render to not use file streaming

    It would be nice to maintain file streaming for better memory usage but it
    prevents the ability to read the file contents previously from within the
    template which is a desire in order to insert into a previous changelog.
    In this case, the memory usage is likely not a problem for large text files.

  • fix(config): prevent jinja from autoescaping markdown content by default

    Since this project is generally rendering non-html content such as RST or MD,
    change the default of the jinja autoescape parameter to false instead of true.
    When it was true, it would automatically convert any & ampersands to its
    htmlentity equivalent & which is completely unnecessary and unreadable in
    non-html documents.

  • docs(configuration): update changelog.environment.autoescape default to false to match code

  • docs(configuration): standardize all true/false to lowercase ensuring toml-compatibility

  • feat(config): add changelog.mode as configuration option

  • feat(config): add changelog.insertion_flag as configuration option

  • refactor(config): use changelog.changelog_file as previous changelog file for target for update

  • style(config): alphabetize changelog configuration options

  • docs(configuration): add changelog.mode and changelog.insertion_flag config definitions

  • fix(changelog): adjust angular heading names for readability

  • feat(changelog): modify changelog template to support changelog updates

    By popular demand, the desire to only prepend new information to the changelog
    is now possible given the changelog.mode = update configuration option.

    Resolves: #​858, #​722

  • refactor(errors): add new generic internal error for tragic improbable flaws

  • fix(changelog): ensure changelog templates can handle complex directory includes

  • feat(config): add changelog.default_templates.output_format config option

  • fix(changelog): only render user templates when files exist

    This change ensures that we will use our default even when the user only overrides
    the release notes template. It also must have jinja templates in the folder otherwise
    we will render the default changelog.

  • refactor(changelog): enable default changelog rendering of multiple template parts

  • refactor(changelog): change rendering of default release notes to new template structure

  • refactor(context): use pathlib instead of context manager to read file

  • test(fixtures): update changelog generator format & angular heading names

  • test(angular): adjust test of commit type to section header

  • test(changelog): update make changelog context function call

  • test(release-notes): update test related to release notes generation

  • test(fixtures): add processing to filter out repo definitions for partial changelogs

  • test(fixtures): update repo generators to update changelogs w/ every version

  • test(fixtures): slow down repo generators to prevent git failures from same timestamps

  • test(fixtures): update changelog generator to include insertion flag

  • refactor(changelog): fix template to handle update when no releases exist

  • refactor(changelog): adjust template to use improved release object

  • refactor(changelog): improve resilence & non-existant initial changelog

  • style(changelog-templates): maintain 2-spaces indentation throughout jinja templates

  • refactor(changelog): ensure cross-platform template includes with jinja compatibility

  • test(changelog-cmd): add tests to evaluate variations of the changelog update mode

  • test(version-cmd): add tests to evaluate variations of the changelog update mode

  • refactor(release-notes): normalize line endings to universal newlines & always end with newline

  • refactor(changelog): ensure default changelog renders w/ universal newlines & writes as os-specific

  • test(changelog): update changelog testing implementation to be newline aware

  • test: update tests to use cross-platform newlines where appropriate

  • docs(changelog-templates): improve detail & describe new changelog.mode="update"

  • docs(configuration): mark version of configuration setting introduction

  • docs(homepage): update custom changelog reference

  • refactor(changelog): adjust read_file filter to read file as os-newline aware

  • refactor(changelog): apply forced universal newline normalizer on default changelog

  • test(changelog): adjust implementation to consistently work on windows

  • test(version): adjust implementation to consistently work on windows

  • refactor(changelog-template): only add insertion flag if in update mode

  • test(changelog): adjust test to handle changelog regeneration in init mode

  • refactor(changelog-templates): adjust init template to clean up extra newlines

  • test(changelog): adjust expected output after cleaned up newlines

  • docs(configuration): define the new changelog.default_templates.output_format option (c18c245)

  • feat(github-actions): add an action build directive to toggle the --skip-build option (#​1044)

  • docs(commands): update definition of the version commands --skip-build option

  • docs(github-actions): add description of the build input directive (26597e2)

v9.9.0

Compare Source

Documentation
  • docs(github-actions): clarify & consolidate GitHub Actions usage docs (#​1011)

    Resolves: #​907

  • chore(scripts): remove non-existant file from version bump script

  • docs(automatic-releases): drop extrenous github push configuration

  • docs(homepage): remove link to old github config & update token scope config

  • docs(github-actions): expand descriptions & clarity of actions configs

  • docs(github-actions): add configuration & description of publish action

  • docs(github-actions): revert removal of namespace prefix from examples (2135c68)

Features
  • feat(github-actions): add is_prerelease output to the version action (#​1038)

  • test(github-actions): add test to ensure is_prerelease is a action output

  • docs(github-actions): add description of new is_prerelease output for version action (6a5d35d)

v9.8.9

Compare Source

Documentation
  • docs: update docstrings to resolve sphinx failures (#​1030)

set ignore-module-all for autodoc_default_options to resolve some
Sphinx errors about duplicate / ambiguous references
https://github.com/sphinx-doc/sphinx/issues/4961#issuecomment-1543858623

Standardize some non-standard (Google-ish) docstrings to Sphinx
format, to avoid ruff and Sphinx arguing about underline length.

Fix indents and other minor whitespace / formatting changes.

Fixes #​1029 (d84efc7)

Fixes
  • fix(version-cmd): improve version_variables flexibility w/ quotes (ie. json, yaml, etc) (#​1028)

  • fix(version-cmd): increase version_variable flexibility with quotations (ie. json, yaml, etc)

    Previously json would not work due to the key being wrapped in quotes, yaml also has issues
    when it does not usually use quotes. The regex we created originally only wrapped the version
    to be replaced in quotes but now both the key and version can optionally be wrapped in
    different kind of quotations.

    Resolves: #​601, #​706, #​962, #​1026

  • docs(configuration): add clarity to version_variables usage & limitations

    Ref: #​941

  • fix(version-cmd): ensure version_variables do not match partial variable names

  • build(deps-test): add PyYAML as a test dependency

  • test(fixtures): refactor location of fixture for global use of cli runner

  • test(stamp-version): add test cases to stamp json, python, & yaml files (156915c)

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)

Fixes
  • 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)

Fixes
  • 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)

Fixes
  • 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

Fixes
  • 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 Improvements
  • 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

Fixes
  • 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

Fixes
  • 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

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

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

v9.8.1

Compare Source

Fixes
  • 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 [email protected] (d911fae)

v9.8.0

Compare Source

Documentation
  • docs(migration-v8): update version references in migration instructions (#​938) (d6ba16a)
Features
  • 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 [email protected] (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 [email protected] (1de6f78)

v9.7.3

Compare Source

Fixes
  • 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)

Fixes
  • 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

Fixes

v9.7.0

Compare Source

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

v9.6.0

Compare Source

Features
  • 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)

Fixes
  • 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 System
Features
  • 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 System
  • 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] [email protected]
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@​users.noreply.github.com> (4a22a8c)

Fixes
  • 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

Fixes
  • 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

Features
  • 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

v8.7.2

Compare Source

Fix
  • fix(lint): correct linter errors (c9556b0)

v8.7.1

Compare Source

Documentation
  • docs(contributing): add docs-build, testing conf, & build instructions (#​787) (011b072)

  • docs(configuration): change defaults definition of token default to table (#​786) (df1df0d)

  • docs: add note on default envvar behaviour (#​780) (0b07cae)

Fix
  • fix(cli-generate-config): ensure configuration types are always toml parsable (#​785) (758e649)

v8.7.0

Compare Source

Feature
  • feat(config): enable default environment token per hvcs (#​774) (26528eb)

v8.6.0

Compare Source

Documentation
  • docs: minor correction to commit-parsing documentation (#​777) (245e878)
Feature
  • feat(utils): expand parsable valid git remote url formats (#​771)

Git remote url parsing now supports additional formats (ssh, https, file, git) (cf75f23)

v8.5.2

Compare Source

Fix
  • fix(cli): gracefully output configuration validation errors (#​772)

  • test(fixtures): update example project workflow & add config modifier

  • test(cli-main): add test for raw config validation error

  • fix(cli): gracefully output configuration validation errors (e8c9d51)

v8.5.1

Compare Source

Documentation
  • docs(configuration): adjust wording and improve clarity (#​766)

  • docs(configuration): fix typo in


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
Copy link

codecov bot commented Feb 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 19.25%. Comparing base (55bbf0a) to head (00179f1).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1084   +/-   ##
=======================================
  Coverage   19.25%   19.25%           
=======================================
  Files          39       39           
  Lines        3496     3496           
  Branches      610      610           
=======================================
  Hits          673      673           
  Misses       2803     2803           
  Partials       20       20           

☔ 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 3 times, most recently from 78dfb11 to 1d3b179 Compare February 14, 2024 22:30
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 1d3b179 to b57bc2d Compare February 25, 2024 11:14
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 4 times, most recently from bc2c3b7 to 4ed6668 Compare March 24, 2024 04:45
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 2 times, most recently from 489e851 to 1f32ff9 Compare April 6, 2024 23:26
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 1f32ff9 to a9b94e5 Compare April 14, 2024 02:32
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 2 times, most recently from 4aa1f70 to 1c41fa7 Compare April 29, 2024 06:26
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 3 times, most recently from 78310fa to fef990e Compare May 10, 2024 16:06
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 2 times, most recently from 5202e6a to e0d9589 Compare May 15, 2024 13:25
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from e0d9589 to 2c6eb43 Compare May 27, 2024 17:07
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 2c6eb43 to 1559bec Compare June 5, 2024 00:42
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 2 times, most recently from 420ec5f to 7c6bbe9 Compare June 18, 2024 08:36
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 2 times, most recently from d3434b7 to 679be50 Compare July 6, 2024 23:16
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 679be50 to 8cbb067 Compare July 20, 2024 13:01
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 8cbb067 to 3e3d19d Compare August 20, 2024 04:48
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 3e3d19d to b35e5b4 Compare September 1, 2024 19:44
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from b35e5b4 to 28f0cca Compare September 27, 2024 10:00
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 28f0cca to ad9f21e Compare September 28, 2024 07:44
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch 4 times, most recently from 1ffb24e to a652a41 Compare October 10, 2024 01:38
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from a652a41 to 8c1bb28 Compare October 13, 2024 01:44
Copy link
Contributor Author

renovate bot commented Oct 13, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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