refactor: migration semantic prefix

[RahulGautamSingh]

Changes

• One more migration from previously huge PR Refactor/migrations #12957

Context

1. Migrate inline with same sort  #11459
2. Refactor/migrations #12957

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[RahulGautamSingh]

Refactoring code logic using the SemanticCommitMessage methods.

[RahulGautamSingh]

Refactoring code logic using the SemanticCommitMessage methods.

Idea dropped needs discussion.
The SemanticCommitMessage returns full prefix as type and returns null for scope ie. unreliable for now.
Eg. for fix(deps):* we get type: fix(deps) , scope:null instead of type: fix , scope:deps

[RahulGautamSingh]

I am in doubt regarding keeping semanticPrefix in depreciated because @pret-a-porter didn't do it in his PR. But from the commit history it seemed we want it depreciated.

PS: I am unable to check the exact PR for migration of semanticPrefix to semanticCommitScope for some reason. If you could link it that would help.

[pret-a-porter]

Refactoring code logic using the SemanticCommitMessage methods.

Idea dropped needs discussion. The SemanticCommitMessage returns full prefix as type and returns null for scope ie. unreliable for now. Eg. for fix(deps):* we get type: fix(deps) , scope:null instead of type: fix , scope:deps

fix(deps):* is not semantic commit message, because it is not follow to specification properly, therefore it will not be parsed by SemanticCommitMessage.fromString
https://www.conventionalcommits.org/en/v1.0.0/#specification
5. A description MUST immediately follow the colon and space after the type/scope prefix.

I still think would be better to use static method SemanticCommitMessage.fromString.

[viceice]

I think this is now blocked, as we hade again issues with that class based semantic commit parsing

[pret-a-porter]

I think this is now blocked, as we hade again issues with that class based semantic commit parsing

What is the issue?

[viceice]

I think this is now blocked, as we hade again issues with that class based semantic commit parsing

What is the issue?

• Bug with commitMessagePrefix in latest Release #16269

[RahulGautamSingh]

I have reverted back to using old logic. We can modify it to use SemanticCommitMessage in future, when it's ready.

[pret-a-porter]

I think this is now blocked, as we hade again issues with that class based semantic commit parsing

What is the issue?

• Bug with commitMessagePrefix in latest Release #16269

Seems like issue in generate script, not in Semantic Commit Message class

[renovate-release]

🎉 This PR is included in version 32.105.2 🎉

The release is available on:

• GitHub release
• 32.105.2

Your semantic-release bot 📦🚀