chore(deps): update group-github-actions (major) #82
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
No release will be made. |
watermarkhu
previously approved these changes
Apr 28, 2025
renovate
bot
force-pushed
the
renovate-major-group-github-actions
branch
from
caee4d7 to
345662a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate-major-group-github-actions
branch
2 times, most recently
from
ec4a446 to
6e2785d
Compare
renovate
bot
force-pushed
the
renovate-major-group-github-actions
branch
from
6e2785d to
ef6bd2e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5->v6v9.21.0->v10.0.2v9.21.0->v10.0.2Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v6Compare Source
python-semantic-release/publish-action (python-semantic-release/publish-action)
v10.0.2Compare Source
v10.0.2 (2025-05-26)
Build System
python-semantic-releasefrom 10.0.1 to 10.0.2 (#63,7198fce)Detailed Changes: v10.0.1...v10.0.2
v10.0.1Compare Source
v10.0.1 (2025-05-25)
Build System
python-semantic-releasefrom 10.0.0 to 10.0.1 (#60,c62a2bc)Detailed Changes: v10.0.0...v10.0.1
v10.0.0Compare Source
v10.0.0 (2025-05-25)
Bug Fixes
1863c50)Build System
python-semantic-releasefrom 9.21.1 to 10.0.0 (#59,155d667)Breaking Changes
root_optionsaction input parameter has been removed because it created a command injection vulnerability for arbitrary code to execute within the container context of the GitHub action if a command injection code was provided as part of theroot_optionsparameter string. To eliminate the vulnerability, each relevant option that can be provided tosemantic-releasehas been individually added as its own parameter and will be processed individually to prevent command injection. Please review our Github Actions Configuration page on the Python Semantic Release Documentation website to review the newly available configuration options that replace theroot_optionsparameter.Resolved Issues
Detailed Changes: v9.21.1...v10.0.0
v9.21.1Compare Source
v9.21.1 (2025-05-05)
Build System
python-semantic-releasefrom 9.21.0 to 9.21.1 (#53,48d162b)Detailed Changes: v9.21.0...v9.21.1
python-semantic-release/python-semantic-release (python-semantic-release/python-semantic-release)
v10.0.2Compare Source
====================
🪲 Bug Fixes
PR#1262,93e23c8).. _93e23c8: python-semantic-release/python-semantic-release@93e23c8
.. _PR#1262https://github.com/python-semantic-release/python-semantic-release/pull/126262
.. _changelog-v10.0.1:
v10.0.1Compare Source
====================
🪲 Bug Fixes
v10.0.0(PR#1255,2803676).. _2803676: python-semantic-release/python-semantic-release@2803676
.. _PR#1255https://github.com/python-semantic-release/python-semantic-release/pull/125555
.. _changelog-v10.0.0:
v10.0.0Compare Source
====================
✨ Features
cmd-version: Enable
version_variablesversion stamp of vars with double-equals(
PR#1244,080e4bc)parser-conventional: Set parser to evaluate all squashed commits by default (
6fcdc99_)parser-conventional: Set parser to ignore merge commits by default (
59bf084_)parser-emoji: Set parser to evaluate all squashed commits by default (
514a922_)parser-emoji: Set parser to ignore merge commits by default (
8a51525_)parser-scipy: Set parser to evaluate all squashed commits by default (
634fffe_)parser-scipy: Set parser to ignore merge commits by default (
d4f128e_)🪲 Bug Fixes
changelog-md: Change to 1-line descriptions in markdown template, closes
#733_ (e7ac155_)changelog-rst: Change to 1-line descriptions in the default ReStructuredText template, closes
#733_ (731466f_)cli: Adjust verbosity parameter to enable silly-level logging (
bd3e7bf_)github-action: Resolve command injection vulnerability in action script (
fb3da27_)parser-conventional: Remove breaking change footer messages from commit descriptions
(
b271cbb_)parser-conventional: Remove issue footer messages from commit descriptions (
b1bb0e5_)parser-conventional: Remove PR/MR references from commit subject line (
eed63fa_)parser-conventional: Remove release notice footer messages from commit descriptions
(
7e8dc13_)parser-emoji: Remove issue footer messages from commit descriptions (
b757603_)parser-emoji: Remove PR/MR references from commit subject line (
16465f1_)parser-emoji: Remove release notice footer messages from commit descriptions (
b6307cb_)parser-scipy: Remove issue footer messages from commit descriptions (
3cfee76_)parser-scipy: Remove PR/MR references from commit subject line (
da4140f_)parser-scipy: Remove release notice footer messages from commit descriptions (
58308e3_)📖 Documentation
Refactor documentation page navigation (
4e52f4b_)algorithm: Remove out-of-date algorithm description (
6cd0fbe_)commit-parsing: Define limitation of revert commits with the scipy parser (
5310d0c_)configuration: Change default value for
allow_zero_versionin the description (203d29d_)configuration: Change the default for the base changelog's
mask_initial_releasevalue(
5fb02ab_)configuration: Change the default value for
changelog.modein the setting description(
0bed906_)configuration: Update
version_variablessection to include double-equals operand support(
PR#1244,080e4bc)contributing: Refactor contributing & contributors layout (
8bed5bc_)github-actions: Add reference to manual release workflow example (
6aad7f1_)github-actions: Change recommended workflow to separate release from deploy (
67b2ae0_)github-actions: Update
python-semantic-release/publish-actionparameter notes (c4d45ec_)github-actions: Update PSR action parameter documentation (
a082896_)upgrading: Re-locate version upgrade guides into
Upgrading PSR(a5f5e04_)upgrading-v10: Added migration guide for v9 to v10 (
4ea92ec_)⚙️ Build System
[email protected](PR#1245,4aa6a6e)♻️ Refactoring
config: Change
allow_zero_versiondefault tofalse(c6b6eab_)config: Change
changelog.default_templates.mask_initial_releasedefault totrue(
0e114c3_)config: Change
changelog.modedefault toupdate(7d39e76_)💥 Breaking Changes
.. seealso::
For a summarized walkthrough, check out our |v10 migration guide|_ as well.
.. _v10 migration guide: ../upgrading/10-upgrade.html
.. |v10 migration guide| replace:: v10 migration guide
changelog-md: The default Markdown changelog template and release notes template will no
longer print out the entire commit message contents, instead, it will only print the commit
subject line. This comes to meet the high demand of better formatted changelogs and requests for
subject line only. Originally, it was a decision to not hide commit subjects that were included in
the commit body via the
git merge --squashcommand and PSR did not have another alternative.At this point, all the built-in parsers have the ability to parse squashed commits and separate
them out into their own entry on the changelog. Therefore, the default template no longer needs to
write out the full commit body. See the commit parser options if you want to enable/disable
parsing squash commits.
changelog-rst: The default ReStructured changelog template will no longer print out the entire
commit message contents, instead, it will only print the commit subject line. This comes to meet
the high demand of better formatted changelogs and requests for subject line only. Originally, it
was a decision to not hide commit subjects that were included in the commit body via the
git merge --squashcommand and PSR did not have another alternative. At this point, all the built-inparsers have the ability to parse squashed commits and separate them out into their own entry on
the changelog. Therefore, the default template no longer needs to write out the full commit body.
See the commit parser options if you want to enable/disable parsing squash commits.
config: This release switches the
allow_zero_versiondefault tofalse. This change isto encourage less
0.xreleases as the default but rather allow the experienced developer tochoose when
0.xis appropriate. There are way too many projects in the ecosystems that neverleave
0.xand that is problematic for the industry tools that help auto-update based onSemVer. We should strive for publishing usable tools and maintaining good forethought for when
compatibility must break. If your configuration already sets the
allow_zero_versionvalue,this change will have no effect on your project. If you want to use
0.xversions, from thestart then change
allow_zero_versiontotruein your configuration.config: This release switches the
changelog.default_templates.mask_initial_releasedefaultto
true. This change is intended to toggle better recommended outputs of the defaultchangelog. Conceptually, the very first release is hard to describe--one can only provide new
features as nothing exists yet for the end user. No changelog should be written as there is no
start point to compare the "changes" to. The recommendation instead is to only list a simple
message as
Initial Release. This is now the default for PSR when providing the very firstrelease (no pre-existing tags) in the changelog and release notes. If your configuration already
sets the
changelog.default_templates.mask_initial_releasevalue, then this change will have noeffect on your project. If you do NOT want to mask the first release information, then set
changelog.default_templates.mask_initial_releasetofalsein your configuration.config: This release switches the
changelog.modedefault toupdate. In this mode, if achangelog exists, PSR will update the changelog IF AND ONLY IF the configured insertion flag
exists in the changelog. The Changelog output will remain unchanged if no insertion flag exists.
The insertion flag may be configured with the
changelog.insertion_flagsetting. When upgradingto
v10, you must add the insertion flag manually or you can just delete the changelog file andrun PSR's changelog generation and it will rebuild the changelog (similar to init mode) but it
will add the insertion flag. If your configuration already sets the
changelog.modevalue, thenthis change will have no effect on your project. If you would rather the changelog be generated
from scratch every release, than set the
changelog.modevalue toinitin yourconfiguration.
github-action: The
root_optionsaction input parameter has been removed because it createda command injection vulnerability for arbitrary code to execute within the container context of
the GitHub action if a command injection code was provided as part of the
root_optionsparameter string. To eliminate the vulnerability, each relevant option that can be provided to
semantic-releasehas been individually added as its own parameter and will be processedindividually to prevent command injection. Please review our
Github Actions Configuration__ pageto review the newly available configuration options that replace the
root_optionsparameter.__ https://github.com/python-semantic-release/python-semantic-release/blob/v10.0.0/docs/configuration/automatic-releases/github-actions.rst
parser-conventional: Any breaking change footer messages that the conventional commit parser
detects will now be removed from the
commit.descriptions[]list but maintained in and only inthe
commit.breaking_descriptions[]list. Previously, the descriptions included all text fromthe commit message but that was redundant as the default changelog now handles breaking change
footers in its own section.
parser-conventional, parser-emoji, parser-scipy: Any issue resolution footers that the parser
detects will now be removed from the
commit.descriptions[]list. Previously, the descriptionsincluded all text from the commit message but now that the parser pulls out the issue numbers the
numbers will be included in the
commit.linked_issuestuple for user extraction in anychangelog generation.
parser-conventional, parser-emoji, parser-scipy: Any release notice footer messages that the
commit parser detects will now be removed from the
commit.descriptions[]list but maintainedin and only in the
commit.notices[]list. Previously, the descriptions included all text fromthe commit message but that was redundant as the default changelog now handles release notice
footers in its own section.
parser-conventional, parser-emoji, parser-scipy: Generally, a pull request or merge request
number reference is included in the subject line at the end within parentheses on some common
VCS's like GitHub. PSR now looks for this reference and extracts it into the
commit.linked_merge_requestand thecommit.linked_pull_requestattributes of a commitobject. Since this is now pulled out individually, it is cleaner to remove this from the first
line of the
commit.descriptionslist (ie. the subject line) so that changelog macros do nothave to replace the text but instead only append a PR/MR link to the end of the line. The
reference does maintain the PR/MR prefix indicator (
#or!).parser-conventional, parser-emoji, parser-scipy: The configuration setting
commit_parser_options.ignore_merge_commitsis now set totrueby default. The feature toignore squash commits was introduced in
v9.18.0and was originally set tofalsetoprevent unexpected results on a non-breaking update. The ignore merge commits feature prevents
additional unnecessary processing on a commit message that likely will not match a commit message
syntax. Most merge commits are syntactically pre-defined by Git or Remote Version Control System
(ex. GitHub, etc.) and do not follow a commit convention (nor should they). The larger issue with
merge commits is that they ultimately are a full copy of all the changes that were previously
created and committed. The merge commit itself ensures that the previous commit tree is
maintained in history, therefore the commit message always exists. If merge commits are parsed,
it generally creates duplicate messages that will end up in your changelog, which is less than
desired in most cases. If you have previously used the
changelog.exclude_commit_patternsfunctionality to ignore merge commit messages then you will want this setting set to
truetoimprove parsing speed. You can also now remove the merge commit exclude pattern from the list as
well to improve parsing speed. If this functionality is not desired, you will need to update your
configuration to change the new setting to
false.parser-conventional, parser-emoji, parser-scipy: The configuration setting
commit_parser_options.parse_squash_commitsis now set totrueby default. The feature toparse squash commits was introduced in
v9.17.0and was originally set tofalseto preventunexpected results on a non-breaking update. The parse squash commits feature attempts to find
additional commits of the same commit type within the body of a single commit message. When
squash commits are found, Python Semantic Release will separate out each commit into its own
artificial commit object and parse them individually. This potentially can change the resulting
version bump if a larger bump was detected within the squashed components. It also allows for the
changelog and release notes to separately order and display each commit as originally written. If
this is not desired, you will need to update your configuration to change the new setting to
false... _#733:https://github.com/python-semantic-release/python-semantic-release/issues/7333
.. _080e4bc: python-semantic-release/python-semantic-release@080e4bc
.. _0bed906: python-semantic-release/python-semantic-release@0bed906
.. _0e114c3: python-semantic-release/python-semantic-release@0e114c3
.. _16465f1: python-semantic-release/python-semantic-release@16465f1
.. _203d29d: python-semantic-release/python-semantic-release@203d29d
.. _3cfee76: python-semantic-release/python-semantic-release@3cfee76
.. _4aa6a6e: python-semantic-release/python-semantic-release@4aa6a6e
.. _4e52f4b: python-semantic-release/python-semantic-release@4e52f4b
.. _4ea92ec: python-semantic-release/python-semantic-release@4ea92ec
.. _514a922: python-semantic-release/python-semantic-release@514a922
.. _5310d0c: python-semantic-release/python-semantic-release@5310d0c
.. _58308e3: python-semantic-release/python-semantic-release@58308e3
.. _59bf084: python-semantic-release/python-semantic-release@59bf084
.. _5fb02ab: python-semantic-release/python-semantic-release@5fb02ab
.. _634fffe: python-semantic-release/python-semantic-release@634fffe
.. _67b2ae0: python-semantic-release/python-semantic-release@67b2ae0
.. _6aad7f1: python-semantic-release/python-semantic-release@6aad7f1
.. _6cd0fbe: python-semantic-release/python-semantic-release@6cd0fbe
.. _6fcdc99: python-semantic-release/python-semantic-release@6fcdc99
.. _731466f: python-semantic-release/python-semantic-release@731466f
.. _7d39e76: python-semantic-release/python-semantic-release@7d39e76
.. _7e8dc13: python-semantic-release/python-semantic-release@7e8dc13
.. _8a51525: python-semantic-release/python-semantic-release@8a51525
.. _8bed5bc: python-semantic-release/python-semantic-release@8bed5bc
.. _a082896: python-semantic-release/python-semantic-release@a082896
.. _a5f5e04: python-semantic-release/python-semantic-release@a5f5e04
.. _b1bb0e5: python-semantic-release/python-semantic-release@b1bb0e5
.. _b271cbb: python-semantic-release/python-semantic-release@b271cbb
.. _b6307cb: python-semantic-release/python-semantic-release@b6307cb
.. _b757603: python-semantic-release/python-semantic-release@b757603
.. _bd3e7bf: python-semantic-release/python-semantic-release@bd3e7bf
.. _c4d45ec: python-semantic-release/python-semantic-release@c4d45ec
.. _c6b6eab: python-semantic-release/python-semantic-release@c6b6eab
.. _d4f128e: python-semantic-release/python-semantic-release@d4f128e
.. _da4140f: python-semantic-release/python-semantic-release@da4140f
.. _e7ac155: python-semantic-release/python-semantic-release@e7ac155
.. _eed63fa: python-semantic-release/python-semantic-release@eed63fa
.. _fb3da27: python-semantic-release/python-semantic-release@fb3da27650ff15b[https://github.com/python-semantic-release/python-semantic-release/pull/1244](https://redirect.github.com/python-semantic-release/python-semantic-release/pull/1244)elease/python-[https://github.com/python-semantic-release/python-semantic-release/pull/1245](https://redirect.github.com/python-semantic-release/python-semantic-release/pull/1245)release/python-semantic-release/pull/1245
.. _changelog-v9.21.1:
v9.21.1Compare Source
====================
🪲 Bug Fixes
#1204_(
PR#1239,f61f8a3)📖 Documentation
PR#1229,550e85f)⚙️ Build System
deps: Bump
richdependency from13.0to14.0(PR#1224,691536e)deps: Expand
python-gitlabdependency to includev5.0.0(PR#1228,a0cd1be).. _#1204:https://github.com/python-semantic-release/python-semantic-release/issues/12044
.. _550e85f: python-semantic-release/python-semantic-release@550e85f
.. _691536e: python-semantic-release/python-semantic-release@691536e
.. _a0cd1be: python-semantic-release/python-semantic-release@a0cd1be
.. _f61f8a3: python-semantic-release/python-semantic-release@f61f8a3
.. _PR#https://github.com/python-semantic-release/python-semantic-release/pull/1224l/1224
.. _PRhttps://github.com/python-semantic-release/python-semantic-release/pull/1228ll/1228
.. _Phttps://github.com/python-semantic-release/python-semantic-release/pull/1229ull/1229
.. _https://github.com/python-semantic-release/python-semantic-release/pull/1239pull/1239
.. _changelog-v9.21.0:
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.