Skip to content

Unified bumping workflow#2749

Merged
RobinTail merged 1 commit intomasterfrom
unified-bumper
Jun 15, 2025
Merged

Unified bumping workflow#2749
RobinTail merged 1 commit intomasterfrom
unified-bumper

Conversation

@RobinTail
Copy link
Copy Markdown
Owner

@RobinTail RobinTail commented Jun 15, 2025 •
edited by coderabbitai Bot
Loading

Related to #2736

Summary by CodeRabbit

  • Chores
    • Updated the version bump workflow with more flexible versioning options and improved input descriptions.
    • Removed separate workflows for minor and patch version bumps, consolidating version management into a single workflow.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 15, 2025 •
edited
Loading

Walkthrough

The changes update the version bumping workflow by renaming and enhancing it to support multiple bump types, including pre-releases. The previous separate minor and patch workflows were deleted, consolidating version management into a single, more flexible workflow. No changes were made to exported or public entities in the codebase.

Changes

Files Change Summary
.github/workflows/bump.yml Renamed workflow to "Version Bump"; updated input descriptions, defaults, and allowed values; enhanced command for dynamic pre-release handling.
.github/workflows/minor.yml,
.github/workflows/patch.yml		 Deleted separate "Minor" and "Patch" version bump workflows, removing their jobs and configuration.

Poem

The rabbits gathered, workflows trimmed,
Old patch and minor, now just a whim.
One bump to rule them, flexible and neat,
Pre-releases and patches, all in one seat.
With every hop, the version grows—
Streamlined, simple, onward it goes! 🐇✨

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

@RobinTail RobinTail marked this pull request as ready for review June 15, 2025 17:00
RobinTail
RobinTail commented Jun 15, 2025
View reviewed changes
Copy link
Copy Markdown
Owner Author

@RobinTail RobinTail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@coveralls-official
Copy link
Copy Markdown

coveralls-official Bot commented Jun 15, 2025

Coverage Status

coverage: 100.0%. remained the same
when pulling 7f87095 on unified-bumper
into 246f1cd on master.

coderabbitai[bot]
coderabbitai Bot reviewed Jun 15, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/bump.yml (1)

50-50: Fix formatting per YAML lint
Remove the trailing spaces on this line and add a newline at end-of-file to satisfy lint rules.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 50-50: no new line character at the end of file

(new-line-at-end-of-file)

[error] 50-50: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 246f1cd and 7f87095.

📒 Files selected for processing (3)
  • .github/workflows/bump.yml (3 hunks)
  • .github/workflows/minor.yml (0 hunks)
  • .github/workflows/patch.yml (0 hunks)
💤 Files with no reviewable changes (2)
  • .github/workflows/minor.yml
  • .github/workflows/patch.yml
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/bump.yml

[error] 50-50: no new line character at the end of file

(new-line-at-end-of-file)

[error] 50-50: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: report
🔇 Additional comments (4)
.github/workflows/bump.yml (4)

1-1: Descriptive workflow name
Renaming the workflow to “Version Bump” clearly conveys its unified purpose.

15-17: Set sensible default bump kind
Defaulting the kind input to "patch" addresses the most common bump scenario and reduces the need for explicit selection.

23-26: Add prerelease bump options
Including premajor, preminor, prepatch, and prerelease provides full flexibility for creating prerelease versions in the unified workflow.

48-50: Dynamic prerelease flag
The inline expression correctly injects --preid beta only when kind starts with pre, streamlining the command for both normal and prerelease bumps.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 50-50: no new line character at the end of file

(new-line-at-end-of-file)

[error] 50-50: trailing spaces

(trailing-spaces)

@RobinTail RobinTail merged commit ad701c2 into master Jun 15, 2025
13 checks passed
@RobinTail RobinTail deleted the unified-bumper branch June 15, 2025 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

Assignees

No one assigned

Labels

CI/CD

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@RobinTail