-
-
Notifications
You must be signed in to change notification settings - Fork 1
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.12.2 #62
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/python-semantic-release-python-semantic-release-9.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.2 #62
renovate
wants to merge
1
commit into
main
from
renovate/python-semantic-release-python-semantic-release-9.x
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #62 +/- ##
=======================================
Coverage 51.14% 51.14%
=======================================
Files 6 6
Lines 614 614
Branches 112 112
=======================================
Hits 314 314
Misses 275 275
Partials 25 25 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
June 18, 2024 06:15
bcacb28
to
1824f68
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.2
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.3
Jun 18, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
June 19, 2024 06:38
1824f68
to
c00d553
Compare
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
June 19, 2024 06:42
c00d553
to
b8e9b9b
Compare
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
June 19, 2024 07:20
b8e9b9b
to
0157a5a
Compare
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
June 19, 2024 07:24
0157a5a
to
99580bf
Compare
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
July 4, 2024 17:25
99580bf
to
a261ec7
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.3
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.4
Jul 4, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
July 7, 2024 00:28
a261ec7
to
f33f4d1
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.4
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.5
Jul 7, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
July 20, 2024 13:13
f33f4d1
to
0f8b709
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.5
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.6
Jul 20, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
August 20, 2024 06:07
0f8b709
to
1d55658
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.6
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.7
Aug 20, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
September 1, 2024 18:08
1d55658
to
3984bee
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.7
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.8
Sep 1, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
September 27, 2024 11:01
3984bee
to
f520d80
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.8
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.9
Sep 27, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
September 28, 2024 07:33
f520d80
to
3bfd5b9
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.8.9
chore(deps): update python-semantic-release/python-semantic-release action to v9.9.0
Sep 28, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
October 7, 2024 10:04
3bfd5b9
to
3d076aa
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.9.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.10.0
Oct 7, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
October 10, 2024 01:48
3d076aa
to
40117b5
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.10.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.10.1
Oct 10, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
October 13, 2024 00:11
40117b5
to
a95561b
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.10.1
chore(deps): update python-semantic-release/python-semantic-release action to v9.11.0
Oct 13, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
October 15, 2024 06:28
a95561b
to
4d92a39
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.11.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.11.1
Oct 15, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
October 18, 2024 06:44
4d92a39
to
9f373b6
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.11.1
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.0
Oct 18, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
November 6, 2024 04:23
9f373b6
to
97e6563
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.1
Nov 6, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
November 7, 2024 04:52
97e6563
to
97ed4ee
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.1
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.2
Nov 7, 2024
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:
v9.8.1
->v9.12.2
Release Notes
python-semantic-release/python-semantic-release (python-semantic-release/python-semantic-release)
v9.12.2
Compare Source
Bug Fixes
fix(hvcs-*): add flexibility to issue & MR/PR url jinja filters (#1089)
fix(github): fix
issue_url
filter to ignore an issue prefix gracefullyfix(github): fix
pull_request_url
filter to ignore an PR prefix gracefullyfix(gitlab): fix
issue_url
filter to ignore an issue prefix gracefullyfix(gitlab): fix
merge_request_url
filter to ignore an PR prefix gracefullyfix(gitea): fix
issue_url
filter to ignore an issue prefix gracefullyfix(gitea): fix
pull_request_url
filter to ignore an PR prefix gracefullyfix(bitbucket): fix
pull_request_url
filter to ignore an PR prefix gracefullytest(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 (
275ec88
)fix(cli): gracefully capture all exceptions unless in very verbose debug mode (#1088)
refactor(cli): consolidate entrypoints into the module execute file (
13ca44f
)v9.12.1
Compare Source
Bug Fixes
fix(cmd-version): fix
--as-prerelease
when no commit change from last full release (#1076) (3b7b772
)fix(changelog): fix raw-inline pattern replacement in
convert_md_to_rst
filter (2dc70a6
)fix(release-notes): add context variable shorthand
ctx
like docs claim & changelog has (d618d83
)Documentation
74f03d4
)v9.12.0
Compare Source
Bug Fixes
fix(parser-emoji): enable the default bump level option (
bc27995
)fix(changelog): ignore commit exclusion when a commit causes a version bump (
e8f886e
)fix(parser-angular): change
Fixes
commit type heading toBug Fixes
(#1064)test(fixtures): update expected changelog heading to
Bug Fixes
test(unit): update expected changelog heading to
Bug Fixes
(09e3a4d
)Documentation
docs(configuration): add deprecation message for the tag parser (
a83b7e4
)docs(commit-parsers): add deprecation message for the tag parser (
af94540
)Features
autofit_text_width
filter to template environment (#1062)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 filtertest(changelog-context): add test cases to check
autofit_text_width
filter use (83e4b86
)v9.11.1
Compare Source
Bug Fixes
a7614b0
)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 determinationfeat(changelog): add
convert_md_to_rst
filter to changelog environmentfeat(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
configurationsetting.
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 formatrefactor(config): move
changelog_file
setting underchangelog.default_templates
This change adds a secondary
changelog_file
setting under the default_templatessection 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 usera 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 rstdocs(configuration): update
output_format
description for reStructuredText supportdocs(configuration): update
changelog_file
with deprecation notice of setting relocationdocs(changelog): clarify the
convert_md_to_rst
filter added to the template environmentdocs(changelog): increase detail about configuration options of default changelog creation (
c2e8831
)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 tothe implied proper regex (
4d12251
)v9.10.0
Compare Source
Documentation
14f04df
)Features
feat(changelog): modify changelog template to support changelog updates (#1045)
feat(changelog): add
read_file
function to changelog template contextThis 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 contextAdds 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 contextThis 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 contextThis 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 envrefactor(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 itshtmlentity equivalent
&
which is completely unnecessary and unreadable innon-html documents.
docs(configuration): update
changelog.environment.autoescape
default tofalse
to match codedocs(configuration): standardize all true/false to lowercase ensuring toml-compatibility
feat(config): add
changelog.mode
as configuration optionfeat(config): add
changelog.insertion_flag
as configuration optionrefactor(config): use
changelog.changelog_file
as previous changelog file for target for updatestyle(config): alphabetize changelog configuration options
docs(configuration): add
changelog.mode
andchangelog.insertion_flag
config definitionsfix(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 optionfix(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
optiondocs(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 outputdocs(github-actions): add description of new
is_prerelease
output for version action (6a5d35d
)v9.8.9
Compare Source
Bug 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 & limitationsRef: #941
fix(version-cmd): ensure
version_variables
do not match partial variable namesbuild(deps-test): add
PyYAML
as a test dependencytest(fixtures): refactor location of fixture for global use of cli runner
test(stamp-version): add test cases to stamp json, python, & yaml files (
156915c
)Documentation
set
ignore-module-all
forautodoc_default_options
to resolve someSphinx 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
)v9.8.8
Compare Source
Bug 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 beingused.
Resolves: #994 (
16e6daa
)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
)v9.8.7
Compare Source
Bug Fixes
fix: provide
context.history
global in release notes templates (#1005)fix(release-notes): provide
context.history
global in release note templatesTemporarily return the
context.history
variable to release notes generationas 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 changelogand 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
)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
vstemplate_dir
option usageProvided additional description that warns about the mutually-exclusive nature of
the
changelog_file
option and thetemplate_dir
option.Resolves: #983 (
a7199c8
)v9.8.6
Compare Source
Bug Fixes
Fixes the command line option for passing a shell command to Powershell. Also included a similar shell detection result for
pwsh (Powershell Core) (
32c8e70
)Documentation
git_committer_name
was repeated; replace one instance of it withgit_committer_email
(ce9ffdb
)v9.8.5
Compare Source
Bug 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*
optsResolves: #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 toO(n)
using alookup 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
Bug Fixes
Resolves: #810 (
348a51d
)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
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 (
0b005df
)v9.8.2
Compare Source
Bug Fixes
fix(templates): suppress extra newlines in default changelog (#954)
Suppress extra newlines in default generated changelog output (
7b0079b
)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated by Mend Renovate. View the repository job log.