fix(util): fixes no-op log output when commit message contains square-brackets by codejedi365 · Pull Request #1287 · python-semantic-release/python-semantic-release
Navigation Menu
{{ message }}
- Notifications You must be signed in to change notification settings
- Fork 266
Merged
codejedi365 merged 1 commit intopython-semantic-release:masterfrom
Jul 1, 2025Conversation
Copy link
Contributor
Purpose
Rationale
How did you test?
How to Verify
PR Completion Checklist
-
Reviewed & followed the Contributor Guidelines
-
Changes Implemented & Validation pipeline succeeds
-
Commits follow the Conventional Commits standard
and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs) -
Appropriate Unit tests added/updated
-
Appropriate End-to-End tests added/updated
-
Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)
…-brackets Resolves: python-semantic-release#1251
codejedi365
changed the title
fix(util): fixes no-op log output when commit message contains square…
fix(util): fixes no-op log output when commit message contains square-brackets
codejedi365
deleted the
fix/rich-log-output
branch
Copy link
Contributor Author
codejedi365
commented
Aug 4, 2025
codejedi365 commented
Aug 4, 2025🎉 This PR has been published as part of v10.3.0 🎉
You can find more information about this release on the GitHub Releases page.
This file contains hidden or 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant