From bc4798063c3d76914368b5389295e6eb957f4b43 Mon Sep 17 00:00:00 2001
From: Danny Brito <54994380+DannyBrito@users.noreply.github.com>
Date: Fri, 17 May 2024 11:50:45 -0400
Subject: [PATCH] docs: update signing details (#250)

* docs: update signing details

* applying suggestions
---
 website/docs/signing.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/website/docs/signing.md b/website/docs/signing.md
index 414fdbb88..1c781c921 100644
--- a/website/docs/signing.md
+++ b/website/docs/signing.md
@@ -1,5 +1,9 @@
 # Signing Packages
 
+:::note
+Available with Dalec release `v0.3.0` and later.
+:::
+
 Packages can be automatically signed using Dalec. To do this, you will
 need to provide a signing frontend. There is an example in the test
 code `test/signer/main.go`. Once that signing image has been built and
@@ -15,6 +19,14 @@ targets: # Distro specific build requirements
         cmdline: "/signer"
 ```
 
+At this time, these targets can leverage package signing:
+
+- `windowscross/zip`
+- `mariner2/rpm`
+- `windowscross/container`
+
+For container targets, only the artifacts within the container get signed.
+
 This will send the artifacts (`.rpm`, `.deb`, or `.exe`) to the
 signing frontend as the build context.