From 9ca9b3c15df72cf8a2f626cca6ef79c9c62aaa41 Mon Sep 17 00:00:00 2001 From: Jeremy Smith Date: Mon, 23 Mar 2026 16:59:32 -0400 Subject: [PATCH 1/2] Update README for current check_bundler.yml workflow --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8928d72..d235165 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ RailsBump uses a few approaches to check whether a gem version is compatible wit Since some gems have a lot of versions and each one needs to be checked against multiple Rails releases, this could get out of hand quickly. To minimize the amount of compatibility checks that need to be done, the gem versions are grouped by their dependencies first. If multiple versions (of the same gem or even of different gems) have the same dependencies, a single check is enough to determine whether all of them are compatible with a specific Rails release or not. -To actually perform the check, [GitHub Actions](https://github.com/features/actions) are used. For each check, a new branch is created in a [separate repository](https://github.com/railsbump/checker), which triggers a [workflow](https://github.com/railsbump/checker/blob/main/.github/workflows/check.yml) that essentially tries to run `bundle lock` and reports the result back to the RailsBump app via a [webhook](https://docs.github.com/en/developers/webhooks-and-events/about-webhooks). +To actually perform the check, we trigger a [GitHub Actions](https://github.com/features/actions) [workflow](https://github.com/railsbump/checker/blob/main/.github/workflows/check_bundler.yml) in a [separate repository](https://github.com/railsbump/checker) that tries to run `bundle install` and reports the result back to the RailsBump app via a webhook. ## History From 4f71b95221574dbfdd9bcbcc2510def37793b009 Mon Sep 17 00:00:00 2001 From: Jeremy Smith Date: Mon, 23 Mar 2026 17:24:54 -0400 Subject: [PATCH 2/2] Minor adjustment --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d235165..bdf96b1 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ RailsBump uses a few approaches to check whether a gem version is compatible wit Since some gems have a lot of versions and each one needs to be checked against multiple Rails releases, this could get out of hand quickly. To minimize the amount of compatibility checks that need to be done, the gem versions are grouped by their dependencies first. If multiple versions (of the same gem or even of different gems) have the same dependencies, a single check is enough to determine whether all of them are compatible with a specific Rails release or not. -To actually perform the check, we trigger a [GitHub Actions](https://github.com/features/actions) [workflow](https://github.com/railsbump/checker/blob/main/.github/workflows/check_bundler.yml) in a [separate repository](https://github.com/railsbump/checker) that tries to run `bundle install` and reports the result back to the RailsBump app via a webhook. +To actually perform the check, we trigger a [GitHub Actions](https://github.com/features/actions) [workflow](https://github.com/railsbump/checker/blob/main/.github/workflows/check_bundler.yml) in a [separate repository](https://github.com/railsbump/checker) that tries to run `bundle install` and reports the result back to the RailsBump app via an API call. ## History