Skip to content

fix: refactor parsing compatibility function to support older custom parsers #1165

Merged
codejedi365 merged 2 commits intopython-semantic-release:masterfrom
codejedi365:fix/parse-return-value-compatibility
Jan 31, 2025
Merged

fix: refactor parsing compatibility function to support older custom parsers #1165
codejedi365 merged 2 commits intopython-semantic-release:masterfrom
codejedi365:fix/parse-return-value-compatibility

Conversation

@codejedi365
Copy link
Copy Markdown
Contributor

@codejedi365 codejedi365 commented Jan 30, 2025

Purpose

Rationale

How did you test?

How to Verify

resolves the error where the casting to a list was incorrectly
implemented causing single results back from custom parsers
(legacy return value) to be mis-interpreted which meant no parse
level would be determined.

Resolves: python-semantic-release#1162
resolves the error where the casting to a list was incorrectly
implemented causing single results back from custom parsers
(legacy return value) to be mis-interpreted which meant no parse
level would be determined.

Resolves: python-semantic-release#1162
@codejedi365 codejedi365 force-pushed the fix/parse-return-value-compatibility branch from 701c470 to fd167fc Compare January 30, 2025 14:36
@codejedi365 codejedi365 merged commit cf340c5 into python-semantic-release:master Jan 31, 2025
@codejedi365 codejedi365 deleted the fix/parse-return-value-compatibility branch January 31, 2025 05:19
@codejedi365
Copy link
Copy Markdown
Contributor Author

🎉 This PR has been published as part of Version 9.18.0 🎉

You can find more information about this release on the GitHub Releases page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Failure to determine correct level bump with custom parser in 9.17.0

1 participant