-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(shorebird_cli): shorebird preview
to not use outdated cached preview artifacts
#2254
fix(shorebird_cli): shorebird preview
to not use outdated cached preview artifacts
#2254
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2254 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 186 186
Lines 5851 5861 +10
=========================================
+ Hits 5851 5861 +10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
packages/shorebird_cli/test/src/commands/preview_command_test.dart
Outdated
Show resolved
Hide resolved
packages/shorebird_cli/test/src/commands/preview_command_test.dart
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ✅
shorebird preview
to not use outdated cached preview artifacts
Co-authored-by: Felix Angelov <felix@shorebird.dev>
Description
When running a preview, the CLI will always use the cache artifact if one if found. This might make the command run an outdated artifact when a release is delete by some reason.
This PR makes the artifact id to be part of the path of the preview artifact, that way, if a release is deleted and recreated, the id will be a fresh one and the cli will not accidentally use the wrong cached artifact.
Fixes #1746
Type of Change