This PR improves the CI workflow, automatizing the crate publishing process, and adding the following rules for Pull Requests:
Pull Request rules
Every Pull Request should have one release label so the auto-release action can correctly bump the semantic version (major.minor.patch). A release label can be:
major: Used when you make incompatible API changes,
mijor: Used when you add functionality in a backwards-compatible manner, and
patch: Used when you make backwards-compatible bug fixes.
For more details about it, check the semver website.
As a reminder: According to the spec-item-4: Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
This PR improves the CI workflow, automatizing the crate publishing process, and adding the following rules for Pull Requests:
Pull Request rules
Every Pull Request should have one
release labelso the auto-release action can correctly bump the semantic version (major.minor.patch). Arelease labelcan be:major: Used when you make incompatible API changes,mijor: Used when you add functionality in a backwards-compatible manner, andpatch: Used when you make backwards-compatible bug fixes.For more details about it, check the semver website.
As a reminder: According to the spec-item-4: Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API
SHOULD NOTbe considered stable.