Configure commits types and releases

[epodivilov]

Hi 👋

I started using the changeset-conventional-commits library and found that it raises patch releases for any commits. However, in conventional commits, it is standard practice that commits like test, chore, etc. do not bump the version.

I have added the following features to the package:

• Set different release rules for different commit types.
• Configure version bumping rules through .changeset/config based on commit types.
• Added a custom JSON schema for the .changeset/config file, which extends the original config with properties for configuring commit types. This provides IDE hints and makes it easier for users to create configurations.

Additionally, I added tests for the function that analyzes commits and generates the corresponding changeset files.

I also fixed the Jest configuration, as it was creating the coverage folder directly in the src directory when running tests, which interfered with the build process. Now, coverage is created at the root of the project. If necessary, I can submit these changes in a separate PR.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e012f13

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR