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.15.0 #228

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 2, 2024

This PR contains the following updates:

Package Type Update Change
relekang/python-semantic-release action minor v9.14.0 -> v9.15.0

Release Notes

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

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


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 Working on dependencies label Dec 2, 2024
@renovate renovate bot requested a review from billsioros as a code owner December 2, 2024 04:04
@renovate renovate bot force-pushed the renovate/relekang-python-semantic-release-9.x branch from 19df153 to ef83f96 Compare December 2, 2024 04:07
Copy link

codecov bot commented Dec 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.40%. Comparing base (f083254) to head (ef83f96).
Report is 163 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #228   +/-   ##
=======================================
  Coverage   65.40%   65.40%           
=======================================
  Files           2        2           
  Lines         237      237           
  Branches       54       54           
=======================================
  Hits          155      155           
  Misses         72       72           
  Partials       10       10           

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

@github-actions github-actions bot merged commit 265feef into master Dec 2, 2024
5 of 6 checks passed
@github-actions github-actions bot deleted the renovate/relekang-python-semantic-release-9.x branch December 2, 2024 04:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎲 dependencies Working on dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants