4.8.3 candidate

[Lee-W]

Description

Checklist

• I have read the contributing guidelines

Code Changes

• Add test cases to all the changes you introduce
• Run poetry all locally to ensure this change passes linter check and tests
• Manually test the changes:
  • Verify the feature/bug fix works as expected in real-world scenarios
  • Test edge cases and error conditions
  • Ensure backward compatibility is maintained
  • Document any manual testing steps performed
• Update the documentation for the changes

Documentation Changes

• Run poetry doc locally to ensure the documentation pages renders correctly

Expected Behavior

Steps to Test This Pull Request

Additional Context

[Lee-W]

Hey @woile @noirbizarre , I'd like to merge this one in the next few days. It contains all the PRs I reviewed this days to avoid bumping version too quickly

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.92%. Comparing base (120d514) to head (d968f26).
Report is 661 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1457      +/-   ##
==========================================
+ Coverage   97.33%   97.92%   +0.59%     
==========================================
  Files          42       58      +16     
  Lines        2104     2704     +600     
==========================================
+ Hits         2048     2648     +600     
  Misses         56       56              

Flag	Coverage Δ
unittests	97.92% <100.00%> (+0.59%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Lee-W]

@bearomorphism, please let us know if you want us to include anything in the next release. We'll try to review them

[bearomorphism]

#1449

[bearomorphism]

and probably #1453 which I'm fixing

[bearomorphism]

and #1442
I'm resolving the conflict

[bearomorphism]

#1428

[bearomorphism]

Those are small PRs (<60 lines of code changes excluding tests). Thanks 🙇

[bearomorphism]

And probably #1466

[Lee-W]

I hope to get it done this week... will try to review some more 💪

[bearomorphism]

@Lee-W pls try merging #1509 to fix CI

[bearomorphism]

@Lee-W It seems that your latest force-push broke things. Could you revert it?

https://github.com/commitizen-tools/commitizen/compare/5a83aebeeed2dbd9a1284b94d5402bb426e70620..baee83e2bdcad7a6e0c7b1cb10082240e87d49d2

[bearomorphism]

This commit is good
5a83aeb

[bearomorphism]

@Lee-W please try #1513

[Lee-W]

I'm a damn idoit 🤦‍♂️

[Lee-W]

@bearomorphism I think i get it restored and push to this one

[bearomorphism]

Please review the followings:

• refactor(bump): eliminate similar patterns in code #1508
• refactor(git): simplify tag logic #1507
• fix(commit): emit deprecated warning of cz commit -s BEFORE going through dialog, add deprecation warning on cz commit --help #1491
• refactor(questions): type questions with TypedDict #1485
• refactor(cz): better typing and refactor message method #1472
• refactor: do not guess if changelog format is provided, make function private #1471
• refactor(check): rename variable and compile pattern once #1470

[bearomorphism]

• refactor(conventional_commits): make schema_pattern more readable #1469

[bearomorphism]

This is also easy to review, thanks

• ci(pyproject.toml): strict check for invalid commit messages #1494