Fix verison validation

[edwardtfn]

Summary by CodeRabbit

• New Features

  • Updated version number to 2024.12.2.
  • Streamlined versioning process by removing the temporary branch creation and consolidating push operations.

• Bug Fixes

  • Improved error handling and commit message logic in the version bump script.
  • Enhanced version format validation and sequence number handling.

• Chores

  • Renamed workflow for clarity and maintained existing trigger conditions.

[coderabbitai]

Walkthrough

This pull request focuses on streamlining the versioning workflow and script. The changes primarily involve modifying the GitHub Actions workflow file and the version bumping script. The workflow now directly pushes changes and tags to the main branch, removing the previous step of creating a temporary branch. The version in the VERSION file has been incremented from 2024.12.1 to 2024.12.2, and the bumping script has been updated to improve version format validation and simplify sequence number handling.

Changes

File	Change Summary
.github/workflows/versioning.yml	- Renamed workflow to "Version Bump and Tag" - Removed temporary branch creation step - Consolidated push changes and tags into a single step
versioning/VERSION	- Version bumped from 2024.12.1 to 2024.12.2
versioning/bump_version.sh	- Updated version format validation regex - Simplified sequence number handling and month reset logic - Retained error handling mechanisms

Possibly related PRs

• New versioning #39: Introduces a new workflow file for versioning, which is directly related to the changes made in the main PR regarding the versioning workflow.
• No leading zero on versions #44: Updates the versioning documentation and includes validation rules that align with the changes made in the main PR, particularly in the bump_version.sh script.
• Use an automation branch #45: Modifies the versioning workflow to incorporate temporary branches, which is relevant to the changes in the main PR that streamline the versioning process.
• Rollback to the last working point #46: Also modifies the versioning workflow, including changes to the paths-ignore section and the removal of unnecessary steps, which relates to the main PR's focus on simplifying the versioning process.

---

📜 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 6767b5e and 360ae31.

📒 Files selected for processing (1)

• versioning/bump_version.sh (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• versioning/bump_version.sh

---

🪧 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.

[coderabbitai]

Actionable comments posted: 1

🔭 Outside diff range comments (1)

versioning/bump_version.sh (1)

Line range hint 16-19: Enhance version format validation

The current validation regex ^[0-9]{4}\.[0-9]{2}\.[0-9]{2}$ ensures basic format but doesn't validate ranges. Consider validating:

1. Month range (01-12)
2. Sequence range (01-99)

-if ! [[ "$CURRENT_VERSION" =~ ^[0-9]{4}\.[0-9]{2}\.[0-9]{2}$ ]]; then
+# Validate format and ranges
+if ! [[ "$CURRENT_VERSION" =~ ^[0-9]{4}\.(0[1-9]|1[0-2])\.(0[1-9]|[1-9][0-9])$ ]]; then
   echo "Error: Invalid version format in $VERSION_FILE"
   exit 1
 fi

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 46c04eb and 6767b5e.

📒 Files selected for processing (3)

• .github/workflows/versioning.yml (1 hunks)
• versioning/VERSION (1 hunks)
• versioning/bump_version.sh (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• versioning/VERSION

🔇 Additional comments (1)

.github/workflows/versioning.yml (1)

Line range hint 36-42: Verify branch protection rules and add validation steps

Direct pushes to the main branch could bypass branch protection rules. Consider:

1. Adding a validation step before pushing
2. Implementing explicit error handling for push failures
3. Verifying that the version bump follows the expected format

Consider adding these safety measures:

1. Version format validation step
2. Explicit error handling for push failures
3. Success/failure notifications