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

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.15.2

Release Notes

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

v9.15.2

Compare Source

Bug Fixes
  • changelog: Ensures user rendered files are trimmed to end with a single newline
    (#​1118,
    6dfbbb0)

  • cli: Add error message of how to gather full error output
    (#​1116,
    ba85532)

  • cmd-version: Enable maintenance prereleases
    (#​864,
    b88108e)

  • test(fixtures): improve changelog generator to filter by max version

  • test(fixtures): add repo fixture of a trunk only repo w/ dual version support

  • test(fixtures): add repo fixture of a trunk only repo w/ dual version support & prereleases

  • test(cmd-version): add rebuild repo tests for new dual version support repos

  • test(version-determination): adjust unit tests of increment_version logic

This clarifies repeated function calls and pytest parameter names included the unclear assert diff.
Adds additional tests to check bad states for failures and refactored to match new function
signature.

  • fix(version-bump): increment based on current commit's history only

Refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology.
This removes the reliance on any last full release that is not within the history of the current
branch.

Resolves: #​861

  • cmd-version: Fix handling of multiple prerelease token variants & git flow merges
    (#​1120,
    8784b9a)
  • refactor: define a custom logging level of silly

  • fix(version): remove some excessive log msgs from debug to silly level

  • test(fixtures): refactor builder functions for version file updates

  • test(fixtures): adjust build command to handle versions w/ build metadata

  • test(fixtures): fix gitflow repo that included an invalid build metadata string

  • test(fixtures): fix major_on_zero setting in repos to match expected behavior

  • test(cmd-version): add test cases to run an example repo rebuild w/ psr

  • test(cmd-version): enable git flow repo rebuild w/ psr test cases

  • fix(cmd-version): handle multiple prerelease token variants properly

In the case where there are alpha and beta releases, we must only consider the previous beta release
even if alpha releases exist due to merging into beta release only branches which have no changes
considerable changes from alphas but must be marked otherwise.

Resolves: #​789

  • fix(cmd-version): fix version determination algorithm to capture commits across merged branches

  • perf(cmd-version): refactor version determination algorithm for accuracy & speed

  • test(algorithm): refactor test to match new function signature

  • style(algorithm): drop unused functions & imports

  • test(algorithm): adapt test case for new DFS commit traversal implementation

  • cmd-version: Forces tag timestamp to be same time as release commit
    (#​1117,
    7898b11)

  • config: Ensure default config loads on network mounted windows environments
    (#​1124,
    a64cbc9)

Resolves: #​1123

  • test(cmd-generate-config): added noop version execution to validate config at runtime

ref: #​1123

v9.15.1

Compare Source

Bug Fixes
  • changelog-md: Fix commit sort of breaking descriptions section
    (75b342e)

  • parser-angular: Ensure issues are sorted by numeric value rather than text sorted
    (3858add)

  • parser-emoji: Ensure issues are sorted by numeric value rather than text sorted
    (7b8d2d9)

v9.15.0

Compare Source

Bug Fixes
  • cmd-version: Ensure release utilizes a timezone aware datetime
    (ca817ed)

  • default-changelog: Alphabetically sort commit descriptions in version type sections
    (bdaaf5a)

Features
  • commit-parser: Enable parsers to flag commit to be ignored for changelog
    (#​1108,
    0cc668c)

This adds an attribute to the ParsedCommit object that allows custom parsers to set to false if it
is desired to ignore the commit completely from entry into the changelog.

Resolves: #​778

  • test(parser-custom): add test w/ parser that toggles if a parsed commit is included in changelog
  • default-changelog: Add a separate formatted breaking changes section
    (#​1110,
    4fde30e)

Resolves: #​244

  • test(fixtures): update repo changelog generator to add breaking descriptions

  • test(default-changelog): add unit tests to demonstrate breaking change descriptions

  • test(release-notes): add unit tests to demonstrate breaking change descriptions

  • feat(changelog-md): add a breaking changes section to default Markdown template

  • feat(changelog-rst): add a breaking changes section to default reStructuredText template

  • feat(changelog-md): alphabetize breaking change descriptions in markdown changelog template

  • feat(changelog-rst): alphabetize breaking change descriptions in ReStructuredText template

  • default-changelog: Alphabetize commit summaries & scopes in change sections
    (#​1111,
    8327068)
  • test(fixtures): force non-alphabetical release history to validate template sorting

  • test(default-changelog): update unit test to enforce sorting of commit desc in version sections

  • test(release-notes): update unit test to enforce sorting of commit desc in version sections

  • feat(changelog-md): alphabetize commit summaries & scopes in markdown changelog template

  • feat(changelog-rst): alphabetize commit summaries & scopes in ReStructuredText template

  • parsers: Enable parsers to identify linked issues on a commit
    (#​1109,
    f90b8dc)
  • refactor(parsers): add parser option validation to commit parsing

  • docs(api-parsers): add option documentation to parser options

  • feat(parsers): add other_allowed_tags option for commit parser options

  • feat(parser-custom): enable custom parsers to identify linked issues on a commit

  • test(parser-angular): add unit tests to verify parsing of issue numbers

  • test(parser-emoji): add unit tests to verify parsing of issue numbers

  • test(parser-scipy): add unit tests to verify parsing of issue numbers

  • fix(util): prevent git footers from being collapsed during parse

  • feat(parser-angular): automatically parse angular issue footers from commit messages

  • feat(parser-emoji): parse issue reference footers from commit messages

  • docs(commit-parsing): improve & expand commit parsing w/ parser descriptions

  • docs(changelog-templates): update examples using new commit.linked_issues attribute

  • chore(docs): update documentation configuration for team publishing

  • release-notes: Add tag comparison link to release notes when supported
    (#​1107,
    9073344)
  • test(release-notes): adjust test case to include a version compare link

  • test(cmd-changelog): add test to ensure multiple variants of release notes are published

v9.14.0

Compare Source

Bug Fixes
  • release-notes: Override default wordwrap to non-wrap for in default template
    (99ab99b)
Documentation
  • changelog-templates: Document new mask_initial_release changelog context variable
    (f294957)

  • configuration: Document new mask_initial_release option usage & effect
    (3cabcdc)

  • homepage: Fix reference to new ci workflow for test status badge
    (6760069)

Features
  • changelog: Add md to rst conversion for markdown inline links
    (cb2af1f)

  • changelog: Define first release w/o change descriptions for default MD template
    (fa89dec)

  • changelog: Define first release w/o change descriptions for default RST template
    (e30c94b)

  • changelog-md: Add markdown inline link format macro
    (c6d8211)

  • changelogs: Prefix scopes on commit descriptions in default template
    (#​1093,
    560fd2c)

  • test(changelog): update default changelog unit tests to handle commit scope

  • test(release-notes): update default release notes unit tests to handle commit scope

  • test(fixtures): update changelog generator fixture to handle scope additions

  • test(cmd-version): update implementation for test resiliency

  • feat(changelog-md): prefix scopes on commit descriptions in Markdown changelog template

  • feat(changelog-rst): prefix scopes on commit descriptions in ReStructuredText template

  • configuration: Add changelog.default_templates.mask_initial_release option
    (595a70b)

  • context: Add mask_initial_release setting to changelog context
    (6f2ee39)

  • release-notes: Define first release w/o change descriptions in default template
    (83167a3)

v9.13.0

Compare Source

Bug Fixes
  • changelog-rst: Ignore unknown parsed commit types in default RST changelog
    (77609b1)

  • parser-angular: Drop the breaking category but still maintain a major level bump
    (f1ffa54)

  • parsers: Improve reliability of text unwordwrap of descriptions
    (436374b)

Documentation
  • changelog-templates: Add linked_merge_request field to examples
    (d4376bc)

  • changelog-templates: Fix api class reference links
    (7a5bdf2)

  • commit-parsing: Add linked_merge_request field to Parsed Commit definition
    (ca61889)

Features
  • changelog: Add PR/MR url linking to default Markdown changelog
    (cd8d131)

Resolves: #​924, #​953

  • changelog: Add PR/MR url linking to default reStructuredText template
    (5f018d6)

Resolves: #​924, #​953

  • parsed-commit: Add linked merge requests list to the ParsedCommit object
    (9a91062)

  • parser-angular: Automatically parse PR/MR numbers from subject lines in commits
    (2ac798f)

  • parser-emoji: Automatically parse PR/MR numbers from subject lines in commits
    (bca9909)

  • parser-scipy: Automatically parse PR/MR numbers from subject lines in commits
    (2b3f738)

Performance Improvements
  • parser-angular: Simplify commit parsing type pre-calculation
    (a86a28c)

  • parser-emoji: Increase speed of commit parsing
    (2c9c468)

  • parser-scipy: Increase speed & decrease complexity of commit parsing
    (2b661ed)

v9.12.2

Compare Source

Bug Fixes
  • cli: Gracefully capture all exceptions unless in very verbose debug mode
    (#​1088,
    13ca44f)
  • refactor(cli): consolidate entrypoints into the module execute file
  • hvcs-*: Add flexibility to issue & MR/PR url jinja filters
    (#​1089,
    275ec88)
  • fix(github): fix issue_url filter to ignore an issue prefix gracefully

  • fix(github): fix pull_request_url filter to ignore an PR prefix gracefully

  • fix(gitlab): fix issue_url filter to ignore an issue prefix gracefully

  • fix(gitlab): fix merge_request_url filter to ignore an PR prefix gracefully

  • fix(gitea): fix issue_url filter to ignore an issue prefix gracefully

  • fix(gitea): fix pull_request_url filter to ignore an PR prefix gracefully

  • fix(bitbucket): fix pull_request_url filter to ignore an PR prefix gracefully

  • test(bitbucket): add test case for prefixed PR numbers

  • test(gitea): add test case for prefixed PR & issue numbers

  • test(gitlab): add test case for prefixed PR & issue numbers

  • test(github): add test case for prefixed PR & issue numbers

  • style(hvcs): fix logical lint errors

  • docs(changelog-templates): update descriptions of issue & MR/PR url jinja filters

v9.12.1

Compare Source

Bug Fixes
  • changelog: Fix raw-inline pattern replacement in convert_md_to_rst filter
    (2dc70a6)

  • cmd-version: Fix --as-prerelease when no commit change from last full release
    (#​1076,
    3b7b772)

  • release-notes: Add context variable shorthand ctx like docs claim & changelog has
    (d618d83)

Documentation
  • contributing: Update local testing instructions
    (74f03d4)

v9.12.0

Compare Source

Bug Fixes
  • changelog: Ignore commit exclusion when a commit causes a version bump
    (e8f886e)

  • parser-angular: Change Fixes commit type heading to Bug Fixes
    (#​1064,
    09e3a4d)

  • test(fixtures): update expected changelog heading to Bug Fixes

  • test(unit): update expected changelog heading to Bug Fixes

  • parser-emoji: Enable the default bump level option
    (bc27995)
Documentation
  • commit-parsers: Add deprecation message for the tag parser
    (af94540)

  • configuration: Add deprecation message for the tag parser
    (a83b7e4)

Features
  • changelog: Add autofit_text_width filter to template environment
    (#​1062,
    83e4b86)

This change adds an equivalent style formatter that can apply a text alignment to a maximum width
and also maintain an indent over paragraphs of text

  • docs(changelog-templates): add definition & usage of autofit_text_width template filter

  • test(changelog-context): add test cases to check autofit_text_width filter use

v9.11.1

Compare Source

Bug Fixes
  • changelog: Prevent custom template errors when components are in hidden folders
    (#​1060,
    a7614b0)

v9.11.0

Compare Source

Features
  • changelog: Add default changelog template in reStructuredText format
    (#​1055,
    c2e8831)
  • 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

  • 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

v9.10.1

Compare Source

Bug Fixes

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

v9.10.0

Compare Source

Documentation
  • github-actions: Update primary example with workflow sha controlled pipeline
    (14f04df)
Features
  • changelog: Modify changelog template to support changelog updates
    (#​1045,
    c18c245)
  • 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

  • github-actions: Add an action build directive to toggle the --skip-build option
    (#​1044,
    26597e2)
  • docs(commands): update definition of the version commands --skip-build option

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

v9.9.0

Compare Source

Documentation
  • github-actions: Clarify & consolidate GitHub Actions usage docs
    (#​1011,
    2135c68)

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

Features
  • github-actions: Add is_prerelease output to the version action
    (#​1038,
    6a5d35d)
  • 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

v9.8.9

Compare Source

Bug Fixes
  • version-cmd: Improve version_variables flexibility w/ quotes (ie. json, yaml, etc)
    (#​1028,
    156915c)
  • 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

Documentation

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

v9.8.8

Compare Source

Bug Fixes
  • config: Fix path traversal detection for windows compatibility
    (#​1014,
    16e6daa)

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

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

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

v9.8.7

Compare Source

Bug Fixes
  • Provide context.history global in release notes templates
    (#​1005,
    5bd91b4)
  • 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.

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

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

  • configuration: Clarify changelog_file vs template_dir option usage
    (a7199c8)

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

Resolves: #​983

  • configuration: Fix build_command_env table rendering
    (#​996,
    a5eff0b)

v9.8.6

Compare Source

Bug Fixes
  • version-cmd: Resolve build command execution in powershell
    (#​980,
    32c8e70)

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

Documentation
  • configuration: Correct GHA parameter name for commit email
    (#​981,
    ce9ffdb)

git_committer_name was repeated; replace one instance of it with git_committer_email

v9.8.5

Compare Source

Bug Fixes
  • Enable --print-last-released* when in detached head or non-release branch
    (#​926,
    782c0a6)
  • 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

Performance Improvements
  • Improve git history processing for changelog generation
    (#​972,
    bfda159)
  • 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

v9.8.4

Compare Source

Bug Fixes
  • changelog-cmd: Remove usage strings when error occured
    (348a51d)

Resolves: #​810

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

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

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

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

  • publish-cmd: Remove usage strings when error occured
    (afbb187)

Resolves: #​810

  • version-cmd: Remove usage strings when error occurred
    (a7c17c7)

Resolves: #​810

v9.8.3

Compare Source

Bug Fixes

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

v9.8.2

Compare Source

Bug Fixes
  • templates: Suppress extra newlines in default changelog
    (#​954,
    7b0079b)

Suppress extra newlines in default generated changelog output

v9.8.1

Compare Source

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

v9.8.0

Compare Source

Documentation
  • migration-v8: Update version references in migration instructions
    (#​938,
    d6ba16a)
Features
  • Extend gitlab to edit a previous release if exists
    (#​934,
    23e02b9)
  • 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]

Resolves: #​936

  • version-cmd: Add toggle of --no-verify option to git commit
    (#​927,
    1de6f78)
  • 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]

v9.7.3

Compare Source

Bug Fixes
  • Enabled prelease-token parameter in github action
    (#​929,
    1bb26b0)

v9.7.2

Compare Source

Bug Fixes
  • Enable user configuration of build_command env vars
    (#​925,
    6b5b271)

  • 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
Documentation
  • configuration: Clarify TOC & alphabetize configuration descriptions
    (19add16)

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

v9.7.1

Compare Source

Bug Fixes
  • gha: Fix missing git_committer_* definition in action
    (#​919,
    ccef9d8)

Resolves: #​918

v9.7.0

Compare Source

Bug Fixes
  • gha: Add missing tag option to GitHub Action definition
    (#​908,
    6b24288)

Resolves: #​906

Documentation
  • configuration: Add description of build command available env variables
    (c882dc6)
Features
  • version-cmd: Pass NEW_VERSION & useful env vars to build command
    (ee6b246)

v9.6.0

Compare Source

Bug Fixes
  • Correct version --prerelease use & enable `--as-prereleas

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 75d8aae to a3d4396 Compare February 8, 2024 09:16
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from a3d4396 to fcf7aea Compare February 8, 2024 13:04
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from fcf7aea to e05b6b5 Compare February 14, 2024 21:20
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from e05b6b5 to 822a5b8 Compare February 25, 2024 09:14
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 822a5b8 to 2008171 Compare March 18, 2024 17:05
Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.05%. Comparing base (f267947) to head (ec270fb).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #70   +/-   ##
=======================================
  Coverage   71.05%   71.05%           
=======================================
  Files           4        4           
  Lines          38       38           
  Branches       11       11           
=======================================
  Hits           27       27           
  Misses          9        9           
  Partials        2        2           

☔ 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 2008171 to 120a7dd Compare March 19, 2024 05:18
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 120a7dd to 162c007 Compare March 21, 2024 06:49
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 162c007 to 89aa857 Compare March 24, 2024 06:19
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 89aa857 to a0f5b68 Compare March 31, 2024 21:52
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from a0f5b68 to 355228f Compare April 6, 2024 22:49
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 355228f to 1a097eb Compare April 14, 2024 03:06
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 1a097eb to 63b623b Compare April 23, 2024 03:34
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 63b623b to cc5f12f Compare April 29, 2024 05:05
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from cc5f12f to 28abf3b Compare May 6, 2024 03:47
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from a768c59 to 8b78262 Compare September 27, 2024 07:52
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 8b78262 to 5333aa7 Compare September 28, 2024 09:41
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 5333aa7 to 37dfbcd Compare October 7, 2024 09:56
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 37dfbcd to 104c78d Compare October 10, 2024 01:10
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 104c78d to 7354eec Compare October 13, 2024 00:41
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 7354eec to 37feced Compare October 15, 2024 07:44
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 37feced to 2a5373f Compare October 18, 2024 07:36
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 2a5373f to c8c014c Compare November 6, 2024 04:55
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from c8c014c to be7cbee Compare November 7, 2024 03:06
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from be7cbee to db48793 Compare November 10, 2024 07:16
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from db48793 to c004668 Compare November 11, 2024 11:00
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from c004668 to dc5a85f Compare December 2, 2024 01:57
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from dc5a85f to 07a140f Compare December 3, 2024 09:15
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 07a140f to ec270fb Compare December 16, 2024 07:15
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