# How can I remove a release from a channel?

**URL:** <https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636>\
**Category:** How do I?\
**Tags:** kots\
**Created:** [January 3, 2022, 1:44pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636 "2022-01-03T13:44:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mariel\_Wilding](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mariel_wilding/32/231_2.png) [@Mariel\_Wilding](https://community.replicated.com/u/Mariel_Wilding)\
**Post date:** [January 3, 2022, 1:44pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/1 "2022-01-03T13:44:59Z")

</div>

You can remove a release in the [Vendor Portal](https://vendor.replicated.com/) by using the archive button (red trash can) on the Releases tab, selecting the release(s) you would like to archive and clicking the **Archive Releases** button.

Alternatively, you can run the command below.

```auto
curl 'https://g.replicated.com/graphql' \
  -H 'authorization: <token>' \
  -H 'content-type: application/json' \
  -H 'accept: */*' \
  --data-raw $'{"operationName":"archiveKotsReleases","variables":{"appId":"<app-id>","sequences":[<sequence-1>, <sequence-2>]},"query":"mutation archiveKotsReleases($appId: ID\u0021, $sequences: [Int]) {\\n archiveKotsReleases(appId: $appId, sequences: $sequences)\\n}\\n"}' \
  --compressed

```

You’ll need to use a user token or a service account token and replace `<token>` in the command with the desired token.

You will also replace `<app-id>`, `<sequence-1>` and `<sequence-2>` with your values.

---

<div class="post-metadata">

**Author:** ![dex](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dex/32/26_2.png) [@dex](https://community.replicated.com/u/dex)\
**Post date:** [January 19, 2022, 1:39pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/2 "2022-01-19T13:39:47Z")

</div>

Does this prevent the release from being installed?

---

<div class="post-metadata">

**Author:** ![Mariel\_Wilding](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mariel_wilding/32/231_2.png) [@Mariel\_Wilding](https://community.replicated.com/u/Mariel_Wilding)\
**Post date:** [January 19, 2022, 2:19pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/3 "2022-01-19T14:19:44Z")

</div>

Yes, however, the release can be unarchived and promoted to a channel if it is needed later or was archived in error.

---

<div class="post-metadata">

**Author:** ![dex](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dex/32/26_2.png) [@dex](https://community.replicated.com/u/dex)\
**Post date:** [January 24, 2022, 3:06am UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/4 "2022-01-24T03:06:54Z")

</div>

Gotcha – thank you!

---

<div class="post-metadata">

**Author:** ![Alex\_Parker](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/alex_parker/32/777_2.png) [@Alex\_Parker](https://community.replicated.com/u/Alex_Parker)\
**Post date:** [December 20, 2023, 1:34pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/5 "2023-12-20T13:34:27Z")

</div>

**Update:** Archiving a release does not remove it from a channel, so it does not prevent it from being pulled by end users. There is currently no way to “take back” a release once it has been promoted to a channel. [Docs](https://docs.replicated.com/vendor/releases-creating-releases#archiving-releases)

---

<div class="post-metadata">

**Author:** ![Chris\_Sanders](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/chris_sanders/32/501_2.png) [@Chris\_Sanders](https://community.replicated.com/u/Chris_Sanders)\
**Post date:** [July 23, 2024, 7:00pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/6 "2024-07-23T19:00:53Z")

</div>

Confirming that this is still accurate as of today.

---

<div class="post-metadata">

**Author:** ![grant](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/grant/32/9_2.png) [@grant](https://community.replicated.com/u/grant)\
**Post date:** [January 27, 2025, 8:33pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/7 "2025-01-27T20:33:47Z")

</div>

the ability to “demote” a channel release is now live: [Managing Releases with the Vendor Portal | Replicated Docs](https://docs.replicated.com/vendor/releases-creating-releases#demote-a-release)

---

<div class="post-metadata">

**Author:** ![Amber\_Alston](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/amber_alston/32/146_2.png) [@Amber\_Alston](https://community.replicated.com/u/Amber_Alston)\
**Post date:** [August 5, 2025, 9:29pm UTC](https://community.replicated.com/t/how-can-i-remove-a-release-from-a-channel/636/8 "2025-08-05T21:29:30Z")

</div>

The customer experience impact of demoting a previously promoted channel release can depend on the installer method your end customer leverages. There is more detail on those considerations in this related article: [What happens downstream when I demote a release in Vendor Portal? (Removing a channel release)](https://community.replicated.com/t/what-happens-downstream-when-i-demote-a-release-in-vendor-portal-removing-a-channel-release/1565)
