Skip to content

Commit c2fb92f

Browse files
authored
feat: clarify the release delete flow (#488)
* feat: clarify the release delete flow * spelling
1 parent 6f3598b commit c2fb92f

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed
76.3 KB
Loading

src/content/docs/code-push/release.mdx

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ sidebar:
77
---
88

99
import { Tabs, TabItem } from '@astrojs/starlight/components';
10+
import { Image } from 'astro:assets';
11+
import releaseDeleteDialog from '~/assets/release_delete_dialog.png';
1012

1113
In order to start pushing updates, you will need to create a release.
1214

@@ -424,6 +426,16 @@ You can delete a release for your app (as defined by your shorebird.yaml) on the
424426
3. Go to the "Settings" tab at the top of the page
425427
4. In the "Danger Zone" there will be a "Delete" button
426428

429+
In order to complete the delete request you do need to confirm which binaries
430+
you would like to be deleted. You can easily delete all releases or pick by
431+
platform. The list of platforms shown is based on the binaries that are uploaded
432+
for that release.
433+
434+
<Image
435+
src={releaseDeleteDialog}
436+
alt="Release Delete Platform Confirm Dialog in Shorebird Console"
437+
/>
438+
427439
## Side-loading and MDM
428440

429441
A common question we get asked is: Does Shorebird require publishing to the App

0 commit comments

Comments
 (0)