Skip to content

feat(parser-conventional): add official conventional-commits parser #1177

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

Conversation

codejedi365
Copy link
Contributor

@codejedi365 codejedi365 commented Feb 9, 2025

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)

NOTICE: The 'angular' commit parser has been renamed to 'conventional' to match
the official conventional-commits standard for which the 'angular' parser has
evolved into. Please update your configurations to specify 'conventional' as
the 'commit_parser' value in place of 'angular'. The 'angular' type will be
removed in v11.
@codejedi365 codejedi365 force-pushed the feat/conventional-commits-parser branch from f950647 to 309577a Compare February 9, 2025 16:36
@codejedi365 codejedi365 merged commit 27ddf84 into python-semantic-release:master Feb 10, 2025
12 checks passed
@codejedi365 codejedi365 deleted the feat/conventional-commits-parser branch February 10, 2025 03:42
@codejedi365
Copy link
Contributor Author

🎉 This PR has been published as part of Version 9.19.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.

1 participant