From 2e9c361f1383af5e83385ab065a40a2f3d7b48f7 Mon Sep 17 00:00:00 2001 From: Jared White Date: Tue, 6 Aug 2024 16:36:36 -0700 Subject: [PATCH] update upgrade instructions --- bridgetown-website/src/_docs/installation/upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bridgetown-website/src/_docs/installation/upgrade.md b/bridgetown-website/src/_docs/installation/upgrade.md index 5f36fe5b1..3434fd99e 100644 --- a/bridgetown-website/src/_docs/installation/upgrade.md +++ b/bridgetown-website/src/_docs/installation/upgrade.md @@ -24,7 +24,7 @@ Sometimes that's as simple as changing your version dotfiles (for example `.ruby To upgrade to Bridgetown 2.0, edit your `Gemfile` to update the version numbers in the argument for the `bridgetown` and `bridgetown-routes` (if applicable) gem to `2.0.0.beta1` and then run `bundle`. {%@ Note type: :warning do %} -We've seen an issue where Bundler won't update a project due to a crash related to the beta version of the new `bridgetown-foundation` gem. Try running `gem install bridgetown-core -v 2.0.0.beta1` first, before running `bundle` or `bundle update`. +We've seen an issue where Bundler won't update a project due to a crash related to the beta version of the new `bridgetown-foundation` gem. Try running `gem install bridgetown-foundation:2.0.0.beta1 bridgetown-core:2.0.0.beta1` first, before running `bundle` or `bundle update`. {% end %} We also recommend you run `bin/bridgetown esbuild update` so you get the latest default esbuild configuration Bridgetown provides, and you may need to update your `esbuild` version in `package.json` as well.