-
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 python-semantic-release/python-semantic-release action to v9.16.1 #13
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.16.1 #13
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
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
August 20, 2024 07:07
14642eb
to
95c4ac1
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:06
95c4ac1
to
0da1b47
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 09:56
0da1b47
to
74ce367
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
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
September 28, 2024 09:05
74ce367
to
ae4b12e
Compare
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
October 7, 2024 09:37
ae4b12e
to
7e3b1c1
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 04:24
7e3b1c1
to
76f5620
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:25
76f5620
to
05b0a4b
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
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
2 times, most recently
from
October 18, 2024 08:43
a3a9464
to
961c79e
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 08:15
961c79e
to
dc7cf71
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 05:01
dc7cf71
to
a4e0113
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
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
November 10, 2024 07:22
a4e0113
to
01c1cac
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.12.2
chore(deps): update python-semantic-release/python-semantic-release action to v9.13.0
Nov 10, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
November 11, 2024 11:07
01c1cac
to
49b4a06
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.13.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.14.0
Nov 11, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
December 2, 2024 01:37
49b4a06
to
fc50a33
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.14.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.15.0
Dec 2, 2024
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.15.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.15.1
Dec 3, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
December 3, 2024 09:39
fc50a33
to
79e0fd8
Compare
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
December 16, 2024 07:14
79e0fd8
to
db05cd2
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.15.1
chore(deps): update python-semantic-release/python-semantic-release action to v9.15.2
Dec 16, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
January 12, 2025 05:37
db05cd2
to
4e4f1fc
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.15.2
chore(deps): update python-semantic-release/python-semantic-release action to v9.16.0
Jan 12, 2025
renovate
bot
force-pushed
the
renovate/python-semantic-release-python-semantic-release-9.x
branch
from
January 12, 2025 21:02
4e4f1fc
to
e83f70a
Compare
renovate
bot
changed the title
chore(deps): update python-semantic-release/python-semantic-release action to v9.16.0
chore(deps): update python-semantic-release/python-semantic-release action to v9.16.1
Jan 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.5
->v9.16.1
Release Notes
python-semantic-release/python-semantic-release (python-semantic-release/python-semantic-release)
v9.16.1
Compare Source
Bug Fixes
(#1142,
c4056fc
)The dynamic import originally would just replace "/" with "." to make the import module name more
pythonic, however this would be problematic in monorepos which would use
"../../misc/commit_parser.py" to locate the parser and so the resulting
sys.modules
entry wouldhave numerous periods (.) as a prefix. This removes that possibility. Still always an issue if the
imported module name matches an existing module but the likelihood is low.
Documentation
(#1140,
9bdd626
)v9.16.0
Compare Source
Bug Fixes
(#1139,
f9a2078
)fix(config-changelog): validate
changelog.exclude_commit_patterns
on config loadtest(fixtures): relocate sanitize changelog functions
test(cmd-version): add test to validate that custom release messages are ignored in changelog
test(config): add
changelog.exclude_commit_patterns
validation checkstyle(config): refactor import names of
re
module--print-tag
result to match configured tag format(#1134,
a990aa7
)test(fixtures): add new trunk repo that has a different tag format
test(fixtures): add helper to extract config settings from repo action definition
test(cmd-version): expand testing of
--print-tag
&--print-last-released-tag
PSR did not have enough testing to demonstrate testing of the tag generation when the tag format was
configured differently than normal. This commit adds a significant portion of testing to exercise
the print tag functionality which must match the configured tag format.
(#1138,
007fd00
)Resolves: #1137
test(fixtures): add new unreleased trunk repo with a different tag format
test(cmd-version): ensure forced bump version on initial release follows tag format
ref: #1137
Features
(#1135,
0418fd8
)test(fixtures): remove import checking/loading of custom parser in
use_custom_parser
test(config): extend import parser unit tests to evaluate file paths to modules
docs(commit-parsing): add the new custom parser import spec description for direct path imports
Resolves: #687
commit_parser
option definition for direct path importsv9.15.2
Compare Source
Bug Fixes
changelog: Ensures user rendered files are trimmed to end with a single newline
(#1118,
6dfbbb0
)cli: Add error message of how to gather full error output
(#1116,
ba85532
)cmd-version: Enable maintenance prereleases
(#864,
b88108e
)test(fixtures): improve changelog generator to filter by max version
test(fixtures): add repo fixture of a trunk only repo w/ dual version support
test(fixtures): add repo fixture of a trunk only repo w/ dual version support & prereleases
test(cmd-version): add rebuild repo tests for new dual version support repos
test(version-determination): adjust unit tests of increment_version logic
This clarifies repeated function calls and pytest parameter names included the unclear assert diff.
Adds additional tests to check bad states for failures and refactored to match new function
signature.
Refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology.
This removes the reliance on any last full release that is not within the history of the current
branch.
Resolves: #861
(#1120,
8784b9a
)refactor: define a custom logging level of silly
fix(version): remove some excessive log msgs from debug to silly level
test(fixtures): refactor builder functions for version file updates
test(fixtures): adjust build command to handle versions w/ build metadata
test(fixtures): fix gitflow repo that included an invalid build metadata string
test(fixtures): fix major_on_zero setting in repos to match expected behavior
test(cmd-version): add test cases to run an example repo rebuild w/ psr
test(cmd-version): enable git flow repo rebuild w/ psr test cases
fix(cmd-version): handle multiple prerelease token variants properly
In the case where there are alpha and beta releases, we must only consider the previous beta release
even if alpha releases exist due to merging into beta release only branches which have no changes
considerable changes from alphas but must be marked otherwise.
Resolves: #789
fix(cmd-version): fix version determination algorithm to capture commits across merged branches
perf(cmd-version): refactor version determination algorithm for accuracy & speed
test(algorithm): refactor test to match new function signature
style(algorithm): drop unused functions & imports
test(algorithm): adapt test case for new DFS commit traversal implementation
cmd-version: Forces tag timestamp to be same time as release commit
(#1117,
7898b11
)config: Ensure default config loads on network mounted windows environments
(#1124,
a64cbc9
)Resolves: #1123
ref: #1123
v9.15.1
Compare Source
Bug Fixes
changelog-md: Fix commit sort of breaking descriptions section
(
75b342e
)parser-angular: Ensure issues are sorted by numeric value rather than text sorted
(
3858add
)parser-emoji: Ensure issues are sorted by numeric value rather than text sorted
(
7b8d2d9
)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
(#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
(#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
(#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
(#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 optionsfeat(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
attributechore(docs): update documentation configuration for team publishing
(#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
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
changelog: Add md to rst conversion for markdown inline links
(
cb2af1f
)changelog: Define first release w/o change descriptions for default MD template
(
fa89dec
)changelog: Define first release w/o change descriptions for default RST template
(
e30c94b
)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
configuration: Add
changelog.default_templates.mask_initial_release
option(
595a70b
)context: Add
mask_initial_release
setting to changelog context(
6f2ee39
)release-notes: Define first release w/o change descriptions in default template
(
83167a3
)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: Add
linked_merge_request
field to examples(
d4376bc
)changelog-templates: Fix api class reference links
(
7a5bdf2
)commit-parsing: Add
linked_merge_request
field to Parsed Commit definition(
ca61889
)Features
(
cd8d131
)Resolves: #924, #953
(
5f018d6
)Resolves: #924, #953
parsed-commit: Add linked merge requests list to the
ParsedCommit
object(
9a91062
)parser-angular: Automatically parse PR/MR numbers from subject lines in commits
(
2ac798f
)parser-emoji: Automatically parse PR/MR numbers from subject lines in commits
(
bca9909
)parser-scipy: Automatically parse PR/MR numbers from subject lines in commits
(
2b3f738
)Performance Improvements
parser-angular: Simplify commit parsing type pre-calculation
(
a86a28c
)parser-emoji: Increase speed of commit parsing
(
2c9c468
)parser-scipy: Increase speed & decrease complexity of commit parsing
(
2b661ed
)v9.12.2
Compare Source
Bug Fixes
(#1088,
13ca44f
)(#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
v9.12.1
Compare Source
Bug Fixes
changelog: Fix raw-inline pattern replacement in
convert_md_to_rst
filter(
2dc70a6
)cmd-version: Fix
--as-prerelease
when no commit change from last full release(#1076,
3b7b772
)release-notes: Add context variable shorthand
ctx
like docs claim & changelog has(
d618d83
)Documentation
(
74f03d4
)v9.12.0
Compare Source
Bug Fixes
changelog: Ignore commit exclusion when a commit causes a version bump
(
e8f886e
)parser-angular: 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
(
bc27995
)Documentation
commit-parsers: Add deprecation message for the tag parser
(
af94540
)configuration: Add deprecation message for the tag parser
(
a83b7e4
)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
feat(config): enable target changelog filename to trigger RST output format
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
configuration: Update
build_command
env table for windows to use all capital vars(
0e8451c
)github-actions: 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>
changelog: Clarify description of the default changelog generation process
(
399fa65
)configuration: 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
(#996,
a5eff0b
)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
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.
🔕 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.