Bundler 2.5.6 Causes Builds to Fail

[OlekKovalevych]

build pack version https://github.com/heroku/heroku-buildpack-ruby/tree/main/changelogs/v267
ruby version: 2.7.2p137

 Building on the Heroku-20 stack
remote: -----> Using buildpacks:
remote:        1. heroku/ruby
remote:        2. heroku/nodejs
remote: -----> Ruby app detected
remote: -----> Installing bundler 2.4.22
remote: -----> Removing BUNDLED WITH version in the Gemfile.lock
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.7.2
remote: -----> Installing dependencies using bundler 2.4.22
remote:        Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 bundle install -j4

exception:

remote:        Fetching gem metadata from https://rubygems.org/.........
remote:        bundler-2.5.6 requires ruby version >= 3.0.0, which is incompatible with the
remote:        current version, 2.7.2
remote:        Bundler Output: Fetching gem metadata from https://rubygems.org/.........
remote:        bundler-2.5.6 requires ruby version >= 3.0.0, which is incompatible with the
remote:        current version, 2.7.2
remote:  !
remote:  !     Failed to install gems via Bundler.
remote:  !
remote:  !     Push rejected, failed to compile Ruby app.
remote: 
remote:  !     Push failed

bundler versions on heroku:

[joshreeves]

Having the same (or similar) issues with v267 build pack. We had to lock our apps to version 266 to be able to deploy.

[OlekKovalevych]

After switching the version to 266, the problem still persists

exception:

[edmorley]

@schneems ^

[Swastik-T]

@OlekKovalevych Did you find any solution to this?

[OlekKovalevych]

@Swastik-T IMO, at the moment there is only one possible solution - to update version of ruby. But I prefer to stay with my current version of ruby(2.7.2).

[supra-man]

@OlekKovalevych @Swastik-T @joshreeves
I was able to fix this issue by clearing heroku app cache
heroku plugins:install heroku-repo
heroku repo:purge_cache -a your-app-name

[Swastik-T]

@supra-man Thanks, man. It worked for me. They should put this in their article.

Clearing cache worked me for the v267 too.

[OlekKovalevych]

@supra-man Thank you a lot! Clearing the cache for me.( also worked for v267 ruby buildpack)

[OlekKovalevych]

Since the problem is solved, I will move issue to a closed one.

[latortuga]

This fix should be included in the changelog because it seems like the changes in #1428 caused this.