-
Notifications
You must be signed in to change notification settings - Fork 57
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 dependency python-semantic-release to v9.8.3 - autoclosed #583
Closed
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-9.x-lockfile
branch
from
March 19, 2024 08:13
ce9ea67
to
9b05a6c
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.2.0
chore(deps): update dependency python-semantic-release to v9.2.2
Mar 19, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
March 21, 2024 08:35
9b05a6c
to
902dca4
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.2.2
chore(deps): update dependency python-semantic-release to v9.3.0
Mar 21, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #583 +/- ##
=======================================
Coverage 89.86% 89.86%
=======================================
Files 19 19
Lines 1125 1125
=======================================
Hits 1011 1011
Misses 114 114 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
March 24, 2024 06:05
902dca4
to
b735d75
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.3.0
chore(deps): update dependency python-semantic-release to v9.3.1
Mar 24, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
March 31, 2024 22:16
b735d75
to
a822c27
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.3.1
chore(deps): update dependency python-semantic-release to v9.4.0
Mar 31, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
April 6, 2024 22:38
a822c27
to
98abe3a
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.4.0
chore(deps): update dependency python-semantic-release to v9.4.1
Apr 6, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
April 14, 2024 05:27
98abe3a
to
496d33f
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.4.1
chore(deps): update dependency python-semantic-release to v9.4.2
Apr 14, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
April 23, 2024 04:54
496d33f
to
3107325
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.4.2
chore(deps): update dependency python-semantic-release to v9.5.0
Apr 23, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
April 29, 2024 07:22
3107325
to
4f950b1
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.5.0
chore(deps): update dependency python-semantic-release to v9.6.0
Apr 29, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
May 6, 2024 03:54
4f950b1
to
818887a
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.6.0
chore(deps): update dependency python-semantic-release to v9.7.0
May 6, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
May 7, 2024 05:20
818887a
to
c7f720a
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.7.0
chore(deps): update dependency python-semantic-release to v9.7.1
May 7, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
May 13, 2024 04:33
c7f720a
to
a515b4d
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.7.1
chore(deps): update dependency python-semantic-release to v9.7.2
May 13, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
May 15, 2024 18:48
a515b4d
to
70b7f52
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.7.2
chore(deps): update dependency python-semantic-release to v9.7.3
May 15, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
May 27, 2024 17:18
70b7f52
to
a294193
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.7.3
chore(deps): update dependency python-semantic-release to v9.8.0
May 27, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
June 5, 2024 01:51
a294193
to
917de74
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.8.0
chore(deps): update dependency python-semantic-release to v9.8.1
Jun 5, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
June 17, 2024 06:35
917de74
to
b3f328a
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.8.1
chore(deps): update dependency python-semantic-release to v9.8.2
Jun 17, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
June 18, 2024 07:23
b3f328a
to
bc89626
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.8.2
chore(deps): update dependency python-semantic-release to v9.8.3
Jun 18, 2024
renovate
bot
force-pushed
the
renovate/python-semantic-release-9.x-lockfile
branch
from
June 20, 2024 11:04
bc89626
to
d826ff2
Compare
renovate
bot
changed the title
chore(deps): update dependency python-semantic-release to v9.8.3
chore(deps): update dependency python-semantic-release to v9.8.3 - autoclosed
Jun 27, 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:
9.1.1
->9.8.3
Release Notes
python-semantic-release/python-semantic-release (python-semantic-release)
v9.8.3
Compare Source
Fix
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
Fix
fix(templates): suppress extra newlines in default changelog (#954)
Suppress extra newlines in default generated changelog output (
7b0079b
)v9.8.1
Compare Source
Fix
fix: improve build cmd env on windows (#942)
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> (
d911fae
)v9.8.0
Compare Source
Documentation
d6ba16a
)Feature
feat: extend gitlab to edit a previous release if exists (#934)
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> (
23e02b9
)Resolves: #936 (
dfb76b9
)feat(version-cmd): add toggle of
--no-verify
option togit commit
(#927)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 line switch on git commit operations that are run with the
version
command.docs(configuration): add
no_git_verify
description to the configuration pageCo-authored-by: bdorsey <brentadorsey@gmail.com> (
1de6f78
)v9.7.3
Compare Source
Fix
prelease-token
parameter in github action (#929) (1bb26b0
)v9.7.2
Compare Source
Documentation
docs(configuration): clarify TOC & alphabetize configuration descriptions (
19add16
)docs(configuration): clarify TOC & standardize heading links (
3a41995
)Fix
build_command
env vars (#925)test(version): add test of user defined env variables in build command
ref: #922
fix(version): enable user config of
build_command
env variablesResolves: #922
docs(configuration): document
build_command_env
configuration option (6b5b271
)v9.7.1
Compare Source
Fix
fix(gha): fix missing
git_committer_*
definition in action (#919)Resolves: #918 (
ccef9d8
)v9.7.0
Compare Source
Documentation
c882dc6
)Feature
NEW_VERSION
& useful env vars to build command (ee6b246
)Fix
fix(gha): add missing
tag
option to GitHub Action definition (#908)Resolves: #906 (
6b24288
)v9.6.0
Compare Source
Feature
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
)Fix
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
)v9.5.0
Compare Source
Build
6bf2849
)Feature
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
Build
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
)Fix
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
)v9.4.1
Compare Source
Fix
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
Feature
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
Fix
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
3690b95
)v9.3.0
Compare Source
Feature
feat(cmd-version): changelog available to bundle (#779)
test(util): fix overlooked file differences in folder comparison
test(version): tracked changelog as changed file on version create
Removes the temporary release_notes hack to prevent CHANGELOG generation on
execution of version command. Now that it is implemented we can remove the
fixture to properly pass the tests.
37fdb28
)v9.2.2
Compare Source
Fix
Refactors configuration loading to use lazy loading by subcommands
triggered by the property access of the runtime_ctx object. Resolves
the issues when running
--help
on subcommands when a configurationis invalid
Resolves: #840 (
91d221a
)v9.2.1
Compare Source
Fix
27cd93a
)v9.2.0
Compare Source
Build
bd892b8
)Documentation
docs(configuration): clarify the
major_on_zero
configuration option (f7753cd
)docs(configuration): add description of
allow-zero-version
configuration option (4028f83
)Feature
feat(version-config): add option to disable 0.x.x versions (
dedb3b7
)feat(version): add new version print flags to display the last released version and tag (
814240c
)Fix
fix(changelog-generation): fix incorrect release timezone determination (
f802446
)fix(changelog): make sure default templates render ending in 1 newline (
0b4a45e
)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.