Update version from 1.0.0 to 1.1.0 in GitHub workflow

[basi]

Problem

The current version in the bump-version.yml workflow is hardcoded to 1.0.0, which prevents proper version bumping for new releases.

Changes

This PR updates the custom_tag value in the GitHub workflow from 1.0.0 to 1.1.0.

Purpose

This change enables proper version bumping for future releases and ensures that the versioning system works as expected.

Impact

After merging this PR, new releases will be properly versioned starting from 1.1.0, and the automatic version bumping mechanism will function correctly for subsequent releases.

Summary by CodeRabbit

• Chores
  • Updated the version tagging to prepare for the upcoming release, advancing the version number from 1.0.0 to 1.1.0.

[coderabbitai]

Walkthrough

The change updates the version tag used by the GitHub Actions workflow. Specifically, the custom_tag parameter in the workflow file has been modified from 1.0.0 to 1.1.0. This update affects the versioning strategy during the tagging process in the repository's CI/CD pipeline.

Changes

File Path	Change Summary
.github/workflows/bump-version.yml	Updated custom_tag parameter value from 1.0.0 to 1.1.0.

---

📜 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 ee1aaf6 and eaa58ff.

📒 Files selected for processing (1)

• .github/workflows/bump-version.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: linux-tests (8.2, mysql)
• GitHub Check: linux-tests (8.0, mysql)
• GitHub Check: linux-tests (8.0, pgsql)

🔇 Additional comments (1)

.github/workflows/bump-version.yml (1)

18-18: Custom Tag Update is Correct.

The change updating custom_tag from 1.0.0 to 1.1.0 correctly aligns with the PR objective. This update will enable the proper version bumping mechanism for future releases. Please double-check that any related documentation or version references in your repository are updated to reflect this new version.

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.