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 python-semantic-release/python-semantic-release action to v9.8.3 #10

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 25, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
python-semantic-release/python-semantic-release action minor v9.1.1 -> v9.8.3

Release Notes

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

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 <[email protected]> (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 <[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

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] <[email protected]>
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)


Configuration

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

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 25, 2024
@renovate renovate bot force-pushed the renovate/python-semantic-release-python-semantic-release-9.x branch from c35d4e4 to b16f9c2 Compare June 25, 2024 16:16
@renovate renovate bot force-pushed the renovate/python-semantic-release-python-semantic-release-9.x branch from b16f9c2 to 19756a8 Compare June 25, 2024 20:12
@renovate renovate bot force-pushed the renovate/python-semantic-release-python-semantic-release-9.x branch from 19756a8 to f99a680 Compare June 25, 2024 21:08
@renovate renovate bot force-pushed the renovate/python-semantic-release-python-semantic-release-9.x branch from f99a680 to c439690 Compare June 26, 2024 00:42
@renovate renovate bot merged commit 9986c91 into main Jun 26, 2024
19 checks passed
@renovate renovate bot deleted the renovate/python-semantic-release-python-semantic-release-9.x branch June 26, 2024 03:39
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