fix:semver

[JarbasAl]

Summary by CodeRabbit

• New Features

  • Added new GitHub Actions workflows for release management and labeling.
  • Introduced automated processes for alpha and stable releases.

• Dependency Updates

  • Updated version constraints for ovos-plugin-manager and ovos-utils.

• Workflow Changes

  • Removed previous release and publish workflows.
  • Streamlined release and publication processes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces significant changes to the GitHub Actions workflows in the .github/workflows/ directory. Several workflows have been removed (propose_release.yml, publish_alpha.yml, publish_release.yml) and replaced with new workflows (conventional-label.yaml, publish_stable.yml, release_workflow.yml). These new workflows aim to streamline the release process, automate version management, and improve continuous integration and deployment. Additionally, the requirements.txt file has been updated with more precise version constraints for two dependencies.

Changes

File	Change Summary
.github/workflows/conventional-label.yaml	New workflow to automatically add labels to pull requests based on conventional release standards
.github/workflows/propose_release.yml	Removed workflow for proposing stable releases
.github/workflows/publish_alpha.yml	Removed workflow for publishing alpha builds
.github/workflows/publish_release.yml	Removed workflow for publishing releases
.github/workflows/publish_stable.yml	New workflow to automate stable release process with jobs for publishing and branch synchronization
.github/workflows/release_workflow.yml	New workflow to automate alpha release, PyPI publishing, and release proposal
requirements/requirements.txt	Updated version constraints for ovos-plugin-manager and ovos-utils

Poem

🐰 Workflows dance, a rabbit's delight,
Releases flowing, smooth and bright
Labels hop, versions take flight
From alpha to stable, code shines tight
Automation's magic, GitHub's might! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 610cd80 and b938f45.

📒 Files selected for processing (7)

• .github/workflows/conventional-label.yaml (1 hunks)
• .github/workflows/propose_release.yml (0 hunks)
• .github/workflows/publish_alpha.yml (0 hunks)
• .github/workflows/publish_release.yml (0 hunks)
• .github/workflows/publish_stable.yml (1 hunks)
• .github/workflows/release_workflow.yml (1 hunks)
• requirements/requirements.txt (1 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.