-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 #75
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/relekang-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.
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
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
February 7, 2024 00:28
450473a
to
af16502
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
February 8, 2024 11:12
af16502
to
77232a5
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
February 14, 2024 21:06
77232a5
to
aefbeba
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
February 25, 2024 10:55
aefbeba
to
c925e3d
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
March 18, 2024 17:06
c925e3d
to
1c1d54b
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #75 +/- ##
=======================================
Coverage 52.40% 52.40%
=======================================
Files 7 7
Lines 708 708
Branches 134 134
=======================================
Hits 371 371
Misses 297 297
Partials 40 40 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
March 19, 2024 07:24
1c1d54b
to
01c25de
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
March 21, 2024 05:26
01c25de
to
985fb6d
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
March 24, 2024 04:48
985fb6d
to
0ed3c59
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
March 31, 2024 22:39
0ed3c59
to
4ced2b2
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
April 6, 2024 21:37
4ced2b2
to
d1238b9
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
April 14, 2024 03:03
d1238b9
to
9e5c76f
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
April 23, 2024 03:03
9e5c76f
to
db7a5a6
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
April 29, 2024 11:20
db7a5a6
to
bcf9896
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
May 6, 2024 03:36
bcf9896
to
4dab278
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
August 20, 2024 05:08
2970bb5
to
eae7b7f
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
September 1, 2024 19:56
eae7b7f
to
667fb05
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
September 27, 2024 07:55
667fb05
to
e8d5d29
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
September 28, 2024 09:37
e8d5d29
to
a1c0d47
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 7, 2024 09:21
a1c0d47
to
92030ed
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 8, 2024 02:05
92030ed
to
f2a40b8
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 8, 2024 03:48
f2a40b8
to
4b98d1d
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 10, 2024 01:09
4b98d1d
to
f769ab3
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 13, 2024 01:46
f769ab3
to
0fd3a60
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 15, 2024 07:00
0fd3a60
to
c864118
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
October 18, 2024 06:18
c864118
to
e090663
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
November 6, 2024 04:20
e090663
to
95d0bf9
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
November 7, 2024 02:24
95d0bf9
to
69406ad
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
November 10, 2024 07:29
69406ad
to
c3116e2
Compare
renovate
bot
force-pushed
the
renovate/relekang-python-semantic-release-9.x
branch
from
November 11, 2024 10:21
c3116e2
to
78603d2
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:
v8.7.2
->v9.14.0
Release Notes
relekang/python-semantic-release (relekang/python-semantic-release)
v9.14.0
Compare Source
Bug Fixes
(
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
context: Add
mask_initial_release
setting to changelog context(
6f2ee39
)configuration: Add
changelog.default_templates.mask_initial_release
option(
595a70b
)release-notes: Define first release w/o change descriptions in default template
(
83167a3
)changelog: Define first release w/o change descriptions for default RST template
(
e30c94b
)changelog: Define first release w/o change descriptions for default MD template
(
fa89dec
)changelog: Add md to rst conversion for markdown inline links
(
cb2af1f
)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
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: Fix api class reference links
(
7a5bdf2
)changelog-templates: Add
linked_merge_request
field to examples(
d4376bc
)commit-parsing: Add
linked_merge_request
field to Parsed Commit definition(
ca61889
)Features
(
5f018d6
)Resolves: #924, #953
(
cd8d131
)Resolves: #924, #953
parser-scipy: Automatically parse PR/MR numbers from subject lines in commits
(
2b3f738
)parser-emoji: Automatically parse PR/MR numbers from subject lines in commits
(
bca9909
)parser-angular: Automatically parse PR/MR numbers from subject lines in commits
(
2ac798f
)parsed-commit: Add linked merge requests list to the
ParsedCommit
object(
9a91062
)Performance Improvements
parser-scipy: Increase speed & decrease complexity of commit parsing
(
2b661ed
)parser-emoji: Increase speed of commit parsing
(
2c9c468
)parser-angular: Simplify commit parsing type pre-calculation
(
a86a28c
)v9.12.2
Compare Source
Bug Fixes
(#1089,
275ec88
)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
(#1088,
13ca44f
)v9.12.1
Compare Source
Bug Fixes
cmd-version: Fix
--as-prerelease
when no commit change from last full release(#1076,
3b7b772
)changelog: Fix raw-inline pattern replacement in
convert_md_to_rst
filter(
2dc70a6
)release-notes: Add context variable shorthand
ctx
like docs claim & changelog has(
d618d83
)Documentation
(
74f03d4
)v9.12.0
Compare Source
Bug Fixes
Enable the default bump level option
(
bc27995
)Ignore commit exclusion when a commit causes a version bump
(
e8f886e
)Change
Fixes
commit type heading toBug Fixes
(#1064,
09e3a4d
)test(fixtures): update expected changelog heading to
Bug Fixes
test(unit): update expected changelog heading to
Bug Fixes
Documentation
Add deprecation message for the tag parser
(
a83b7e4
)Add deprecation message for the tag parser
(
af94540
)Features
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 filtertest(changelog-context): add test cases to check
autofit_text_width
filter usev9.11.1
Compare Source
Bug Fixes
(#1060,
a7614b0
)v9.11.0
Compare Source
Features
(#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 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
configuration setting.Resolves: #399
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_templates section whiledeprecating 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 newsetting 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 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
v9.10.1
Compare Source
Bug Fixes
(#1054,
4d12251
)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 regexv9.10.0
Compare Source
Documentation
(
14f04df
)Features
(#1045,
c18c245
)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.
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.
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.
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.
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 unnecessaryand unreadable in non-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
optionbuild
directive to toggle the--skip-build
option(#1044,
26597e2
)docs(commands): update definition of the version commands
--skip-build
optiondocs(github-actions): add description of the
build
input directivev9.9.0
Compare Source
Documentation
(#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
is_prerelease
output to the version action(#1038,
6a5d35d
)test(github-actions): add test to ensure
is_prerelease
is a action outputdocs(github-actions): add description of new
is_prerelease
output for version actionv9.8.9
Compare Source
Bug Fixes
version_variables
flexibility w/ quotes (ie. json, yaml, etc)(#1028,
156915c
)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
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
Documentation
(#1030,
d84efc7
)set
ignore-module-all
forautodoc_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
(#1014,
16e6daa
)The original implementation of the path traversal detection expected that
resolve()
works the sameon 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
Update
build_command
env table for windows to use all capital vars(
0e8451c
)Update version in examples to latest version
(
3c894ea
)v9.8.7
Compare Source
Bug Fixes
context.history
global in release notes templates(#1005,
5bd91b4
)context.history
global in release note templatesTemporarily return the
context.history
variable to release notes generation as many users areusing 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 notesfunctionality.
Resolves: #984
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
(#1004,
5fdf761
)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>
Fix build_command_env table rendering
(#996,
a5eff0b
)Clarify description of the default changelog generation process
(
399fa65
)Clarify
changelog_file
vstemplate_dir
option usage(
a7199c8
)Provided additional description that warns about the mutually-exclusive nature of the
changelog_file
option and thetemplate_dir
option.Resolves: #983
v9.8.6
Compare Source
Bug Fixes
(#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
(#981,
ce9ffdb
)git_committer_name
was repeated; replace one instance of it withgit_committer_email
v9.8.5
Compare Source
Bug Fixes
--print-last-released*
when in detached head or non-release branch(#926,
782c0a6
)ref: #900
--print-last-released*
optsResolves: #900
Performance Improvements
(#972,
bfda159
)This converts the double for-loop (
O(n^2)
) down toO(n)
using a lookup table to match thecurrent commit with a known tag rather than iterating through all the tags of the repository every
time.
v9.8.4
Compare Source
Bug Fixes
(
348a51d
)Resolves: #810
(
afbb187
)Resolves: #810
Prevent path traversal manipulation of target changelog location
(
43e35d0
)Remove usage strings when error occurred
(
a7c17c7
)Resolves: #810
Prevent error when provided tag does not exist locally
(
16afbbb
)Prevent path traversal manipulation of target changelog location
(
3eb3dba
)Render default changelog when user template directory exist but is empty
(
bded8de
)v9.8.3
Compare Source
Bug Fixes
(#956,
0b005df
)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
(#954,
7b0079b
)Suppress extra newlines in default generated changelog output
v9.8.1
Compare Source
Bug Fixes
(#942,
d911fae
)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 jcmencia@arsys.es
v9.8.0
Compare Source
Documentation
(#938,
d6ba16a
)Features
(#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 brentadorsey@gmail.com
(#937,
dfb76b9
)Resolves: #936
--no-verify
option togit 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 togit commit
This commit adds a configuration option that toggles the addition of
--no-verify
command lineswitch on git commit operations that are run with the
version
command.no_git_verify
description to the configuration pageCo-authored-by: bdorsey brentadorsey@gmail.com
v9.7.3
Compare Source
Bug Fixes
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
build_command
env variablesResolves: #922
build_command_env
configuration optionDocumentation
Clarify TOC & alphabetize configuration descriptions
(
19add16
)Clarify TOC & standardize heading links
(
3a41995
)v9.7.1
Compare Source
Bug Fixes
fix(gha): fix missing
git_committer_*
definition in action (#919)Resolves: #918 (
ccef9d8
)v9.7.0
Compare Source
Bug Fixes
fix(gha): add missing
tag
option to GitHub Action definition (#908)Resolves: #906 (
6b24288
)Documentation
c882dc6
)Features
NEW_VERSION
& useful env vars to build command (ee6b246
)v9.6.0
Compare Source
Bug Fixes
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
usePrior to this change,
--prerelease
performed the role of converting whichever forcedversion 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 disabledthe ability to force a prerelease.
Resolves: #639
feat(version-cmd): add
--as-prerelease
option to force the next version to be a prereleasePrior 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
)Features
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
)v9.5.0
Compare Source
Build System
6bf2849
)Features
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
Bug Fixes
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 valuesResolves: #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
)Build System
Updates the requirements on rich to permit the latest version.
Resolves: #888
Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (
4a22a8c
)v9.4.1
Compare Source
Bug Fixes
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
Features
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
Bug Fixes
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
)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 Improvements
3690b95
](https://redirect.github.com/python-semantic-release/python-semantic-release/commit/369Configuration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.