Skip to content

chore(main): release 0.1.0 - #2

Merged
asjer merged 1 commit into
mainfrom
release-please--branches--main--components--rails-worktrees
Mar 30, 2026
Merged

asjer merged 1 commit into
mainfrom
release-please--branches--main--components--rails-worktrees

Conversation

@asjer

@asjer asjer commented Mar 30, 2026 •

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

0.1.0 (2026-03-30)

Features

  • add wt command and rails installer (5d798d5)

This PR was generated with Release Please. See documentation.

Copilot AI review requested due to automatic review settings March 30, 2026 13:12

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Cuts the first stable release by bumping the gem version to 1.0.0 and recording the release notes produced by Release Please.

Changes:

  • Bump Rails::Worktrees::VERSION to 1.0.0
  • Update Gemfile.lock to reflect the new local gem version
  • Add 1.0.0 (2026-03-30) release entry to CHANGELOG.md and update release-please manifest

Reviewed changes

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

File Description
lib/rails/worktrees/version.rb Updates the gem’s version constant to 1.0.0.
Gemfile.lock Updates the PATH gem version entry for rails-worktrees.
CHANGELOG.md Adds the 1.0.0 release section above Unreleased notes.
.release-please-manifest.json Bumps release-please tracked version to 1.0.0.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coderabbitai

coderabbitai Bot commented Mar 30, 2026 •

Copy link
Copy Markdown

Warning

Rate limit exceeded

@asjer has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 27 minutes and 11 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 27 minutes and 11 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a10ea677-afef-4b10-8f30-8286f5f27da7

📥 Commits

Reviewing files that changed from the base of the PR and between 98c0344 and f2da625.

⛔ Files ignored due to path filters (1)
  • Gemfile.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • .release-please-manifest.json
  • CHANGELOG.md
📝 Walkthrough

Walkthrough

Updated release metadata, changelog, and Ruby version constant: .release-please-manifest.json now maps the root package to "0.1.0", CHANGELOG.md gains a 0.1.0 release entry (2026-03-30), and lib/rails/worktrees/version.rb updates the VERSION from '0.0.0' to '1.0.0'.

Changes

Cohort / File(s) Summary
Release & Version Files
/.release-please-manifest.json, CHANGELOG.md, lib/rails/worktrees/version.rb
Added root package mapping ".": "0.1.0" to the release manifest, inserted ## 0.1.0 (2026-03-30) with feature note in the changelog, and bumped Rails::Worktrees::VERSION from '0.0.0' to '1.0.0'.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 I hopped from zero into one today,
A tiny stamp upon the way,
Manifest and changelog say hooray,
VERSION set — let's romp and play! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore(main): release 0.1.0' accurately describes the pull request, which creates a release for version 0.1.0 by updating version files and the changelog.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--rails-worktrees

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@asjer asjer changed the title chore(main): release 1.0.0 chore(main): release 0.1.0 Mar 30, 2026
@asjer
asjer force-pushed the release-please--branches--main--components--rails-worktrees branch from c8ea3ee to 98c0344 Compare March 30, 2026 13:48
@asjer
asjer force-pushed the release-please--branches--main--components--rails-worktrees branch from 98c0344 to e39a574 Compare March 30, 2026 13:53
@asjer asjer self-assigned this Mar 30, 2026
@asjer asjer added release-please:force-run Let release-please re-process the branch autorelease: pending and removed autorelease: pending release-please:force-run Let release-please re-process the branch labels Mar 30, 2026
@asjer
asjer force-pushed the release-please--branches--main--components--rails-worktrees branch 2 times, most recently from 6b36691 to 473d500 Compare March 30, 2026 14:44
@asjer
asjer force-pushed the release-please--branches--main--components--rails-worktrees branch from 473d500 to f2da625 Compare March 30, 2026 14:46
@asjer
asjer merged commit 575d6fc into main Mar 30, 2026
5 checks passed
@asjer

asjer commented Mar 30, 2026

Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants