From 13b899325231233b5fbe4ee01473674538ebdd7c Mon Sep 17 00:00:00 2001 From: crimson-knight Date: Sat, 7 Nov 2026 11:37:17 -0500 Subject: [PATCH 1/2] Guide: pin the tap commit for 2.0.10; say what upgrading Minecart changes --- docs/ONBOARDING.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/ONBOARDING.md b/docs/ONBOARDING.md index 790b921..6f0e804 100644 --- a/docs/ONBOARDING.md +++ b/docs/ONBOARDING.md @@ -29,7 +29,7 @@ brew tap amberframework/amber_cli brew trust --tap amberframework/amber_cli tap_path="$(brew --repo amberframework/amber_cli)" git -C "$tap_path" fetch origin -git -C "$tap_path" checkout --detach 018819c6340135c7b0d5b9767640e8ff9ad23491 +git -C "$tap_path" checkout --detach 8493998f2c5524fdfa72246ed0ce08a3883d6c90 HOMEBREW_NO_AUTO_UPDATE=1 brew install amberframework/amber_cli/amber_cli ``` @@ -91,6 +91,9 @@ Teammates who clone the app run one command to install exactly what the lock say minecart install --frozen ``` +Everyone on the team uses Minecart 2025.11.25.9 or newer, the version these steps +install. An older Minecart reports a checksum mismatch on this `shard.lock`. + ## 4. See the rules work Amber ships its rules with the framework, and they apply with no setup. Print the @@ -154,6 +157,7 @@ dependencies: ```bash minecart update mica +grep -A2 '^ mica:' shard.lock # checksum: sha256-v2:f13de354cf66409ccbc1e975f08b23e230620fc895309d057b7ba79aa07ce4e4 ``` Then register it in `config/initializers/request_body_parsers.cr`: @@ -196,5 +200,9 @@ grep -A2 '^ amber:' shard.lock # checksum: sha256-v2:8d354db3b41625db0362162a amber setup:agent ``` +`git-tree:` entries already in your lock keep verifying, and Minecart prints a +notice about them. Minecart 2025.11.25.9 stops on a folder in `lib/` that +`shard.lock` does not pin, and names it. Remove that folder and install again. + Then read the [beta.10 release notes](https://github.com/amberframework/amber/blob/v2.0.0-beta.10/RELEASE_NOTES_V2_BETA10.md). From f0955867deaa823b62ec623c33086d0d4658f46d Mon Sep 17 00:00:00 2001 From: crimson-knight Date: Sat, 7 Nov 2026 11:43:48 -0500 Subject: [PATCH 2/2] Guide: show the checksum line in the lock checks --- docs/ONBOARDING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ONBOARDING.md b/docs/ONBOARDING.md index 6f0e804..a55021a 100644 --- a/docs/ONBOARDING.md +++ b/docs/ONBOARDING.md @@ -157,7 +157,7 @@ dependencies: ```bash minecart update mica -grep -A2 '^ mica:' shard.lock # checksum: sha256-v2:f13de354cf66409ccbc1e975f08b23e230620fc895309d057b7ba79aa07ce4e4 +grep -A3 '^ mica:' shard.lock # checksum: sha256-v2:f13de354cf66409ccbc1e975f08b23e230620fc895309d057b7ba79aa07ce4e4 ``` Then register it in `config/initializers/request_body_parsers.cr`: @@ -196,7 +196,7 @@ dependencies: ```bash minecart update amber -grep -A2 '^ amber:' shard.lock # checksum: sha256-v2:8d354db3b41625db0362162a34836fe10a8b11a378f3837d34cc6bbcece1cb94 +grep -A3 '^ amber:' shard.lock # checksum: sha256-v2:8d354db3b41625db0362162a34836fe10a8b11a378f3837d34cc6bbcece1cb94 amber setup:agent ```