@@ -31,6 +31,10 @@ jobs:
               xargs -0 shellcheck --check-sourced --color=always
 
   integration-test:
+      # Only runs on the upstream repo, which holds the required secrets
+      # (HEROKU_API_KEY, etc.). Forks don't have access, so the job would
+      # always fail at the Hatchet setup step.
+      if: github.repository == 'heroku/heroku-buildpack-ruby'
       runs-on: ubuntu-24.04
       env:
         HATCHET_APP_LIMIT: 300
 
@@ -2,6 +2,9 @@
 
 ## [Unreleased]
 
+- Fork-only: honor `BUNDLE_GEMFILE` (typically a Heroku config var) so the buildpack can deploy either the current Gemfile or a next_rails-style alternative (e.g. `Gemfile.next`). Defaults to `Gemfile`, so behavior is unchanged when `BUNDLE_GEMFILE` is not set. Includes a build-time materializer that rewrites a `Gemfile.next` symlink as a real file so the `File.basename(__FILE__)` dual-boot trick works deterministically across Bundler versions.
+- Fork-only: skip the `integration-test` workflow on forks (the job requires Heroku API secrets only available on the upstream repo).
+
 
 ## [v359] - 2026-05-20