build(deps-dev): bump commitizen from 2.42.1 to 3.31.0

[dependabot]

Bumps commitizen from 2.42.1 to 3.31.0.

Release notes

Sourced from commitizen's releases.

v3.31.0 (2024-11-16)

Feat

• commitizen: document '--' double dash in '--help'

Fix

• commit: avoid warnings with 'always_signoff' configuration
• commit: resolve 'always_signoff' configuration and '-s' CLI issues

[master d3f092d9] bump: version 3.30.1 → 3.31.0 4 files changed, 15 insertions(+), 4 deletions(-)

v3.30.1 (2024-11-10)

Refactor

• cli: replace magic number 0 with ExitCode.EXPECTED_EXIT
• defaults: disallow style as None
• cz_customize: return empty string for info, example, schema and schema_pattern if not provided

[master 665aa59a] bump: version 3.30.0 → 3.30.1 4 files changed, 12 insertions(+), 4 deletions(-)

v3.30.0 (2024-10-23)

Feat

• commands/commit: add force-edit functionality after answering questions

Refactor

• remove redundant return None

[master bfe422fa] bump: version 3.29.1 → 3.30.0 4 files changed, 14 insertions(+), 4 deletions(-)

v3.29.1 (2024-09-26)

Fix

• changelog: Factorized TAG_FORMAT_REGEXES
• changelog: Handle tag format without version pattern
• changelog: handle custom tag_format in changelog generation

Refactor

• Use format strings

... (truncated)

Changelog

Sourced from commitizen's changelog.

v3.31.0 (2024-11-16)

Feat

• commitizen: document '--' double dash in '--help'

Fix

• commit: avoid warnings with 'always_signoff' configuration
• commit: resolve 'always_signoff' configuration and '-s' CLI issues

v3.30.1 (2024-11-10)

Refactor

• cli: replace magic number 0 with ExitCode.EXPECTED_EXIT
• defaults: disallow style as None
• cz_customize: return empty string for info, example, schema and schema_pattern if not provided

v3.30.0 (2024-10-23)

Feat

• commands/commit: add force-edit functionality after answering questions

Refactor

• remove redundant return None

v3.29.1 (2024-09-26)

Fix

• changelog: Factorized TAG_FORMAT_REGEXES
• changelog: Handle tag format without version pattern
• changelog: handle custom tag_format in changelog generation

Refactor

• Use format strings

v3.29.0 (2024-08-11)

Feat

• bump: add functionality to write the next version to stdout

v3.28.0 (2024-07-17)

Feat

... (truncated)

Commits

• d3f092d bump: version 3.30.1 → 3.31.0
• 9c891d6 test(conftest): disable 'safe.directory' Git config for container bound sources
• 9aa3076 feat(commitizen): document '--' double dash in '--help'
• 02dd9d0 docs(gettings_started): migrate to 'cz commmit -- -s' syntaxes
• 18e4928 fix(commit): avoid warnings with 'always_signoff' configuration
• 26be522 fix(commit): resolve 'always_signoff' configuration and '-s' CLI issues
• d017869 ci(deps): bump codecov/codecov-action from 4 to 5
• 4d6f610 build(deps-dev): bump ruff from 0.7.2 to 0.7.3
• e4cab6c build(deps): bump packaging from 24.1 to 24.2
• f41a88e ci(github-actions): use 3.13 instead of 3.13-dev as Python 3.13 has already b...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
pypi/[email protected]	None	0	41.6 kB	Willemoes
pypi/[email protected]	environment, eval, filesystem, network, shell	0	1.78 MB	jonathan.slenders
pypi/[email protected]	environment	0	104 kB	tmbo

🚮 Removed packages: pypi/[email protected], pypi/[email protected], pypi/[email protected], pypi/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
AI-detected potential code anomaly	pypi/[email protected]	Notes: The code contains multiple potential security risks, including unauthorized file writes, command injection, information leakage, and code injection. It should be reviewed and modified to ensure proper input validation, sanitization, and secure handling of user input. The presence of 'eval' raises concerns about the safety and security of the code. Confidence: 0.80 Severity: 0.70	poetry.lock	🚫

View full report↗︎

Next steps

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore pypi/[email protected]