Why does it take so much time for patching sometimes? Does it mean we cannot always use patches? Or how do we know if the patch is working this time or not?
shorebird patch android --flavor prod --target lib/env/prod/main.dart -- --dart-define ....
✓ Fetching apps (0.6s)
✓ Building patch with Flutter 3.19.6 (4b22a31bd9) (20.7s)
✓ Detected release version 2.2.11+100 (0.3s)
✓ Fetching releases (0.5s)
Release was built with Flutter revision aee5222c0d52012f089564a8395826d56e7c2fe8
✓ Building patch (100.9s)
✓ Fetching release artifacts (1.1s)
✓ Fetching aab artifact (0.3s)
✓ Downloading release artifacts (1147.9s)
✓ Verifying patch can be applied to release (0.1s)
[WARN] Your app contains asset changes, which will not be included in the patch.
Changed files:
base/assets/flutter_assets/fonts/MaterialIcons-Regular.otf
Continue anyways? (y/N) Yes
✓ Creating artifacts (19.7s)
:rocket: Ready to publish a new patch!
:mobile_phone: App: appname (prod) (....)
:shaved_ice: Flavor: prod
:package: Release Version: 2.2.11+100
:joystick: Platform: android [arm32 (1.58 MB), arm64 (1.49 MB), x86_64 (1.49 MB)]
:green_circle: Track: Production
Would you like to continue? (y/N) Yes
✓ Creating patch (2.2s)
✓ Uploading artifacts (7.3s)
✓ Fetching channels (0.4s)
✓ Promoting patch to stable (0.4s)
:white_check_mark: Published Patch 3!
Does using the Shorebird patch command or release command reduce the space on my laptop hard disk? If so, how can I clean up after releasing or patching?