From 31ae40c2069fad2c4b6f0708aa929d5191d1004a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Cortier?=
 <3809077+CBenoit@users.noreply.github.com>
Date: Fri, 14 Mar 2025 10:00:44 +0100
Subject: [PATCH] chore: only publish GitHub releases for ironrdp-client (#704)

Creating a new GitHub release for the ironrdp crate is actually not very
relevant.
---
 release-plz.toml | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/release-plz.toml b/release-plz.toml
index b0dbeb14..79409f23 100644
--- a/release-plz.toml
+++ b/release-plz.toml
@@ -7,10 +7,7 @@ pr_name = "chore(release): prepare for publishing"
 changelog_config = "cliff.toml"
 release_commits = "^(feat|docs|fix|build|perf)"
 
-# Flagship crates for which we push a GitHub release.
-[[package]]
-name = "ironrdp"
-git_release_enable = true
+# Flagship crate for which we push a GitHub release.
 [[package]]
 name = "ironrdp-client"
 git_release_enable = true
@@ -24,7 +21,7 @@ publish_features = ["rustls"]
 # *-native crates may have all kinds of system requirements depending on the platform.
 # We can only check for the current platform when cargo publish is invoked, all the others are effectively unverified.
 # For this reason, it's not worth complexifying the release-crates.yml workflow.
-# We already verify all targets properly in the CI.
+# We already verify all targets properly in the regular CI workflow.
 [[package]]
 name = "ironrdp-rdpdr-native"
 publish_no_verify = true