From 533786cd10df6d64adb03971475b3cff3c9709b4 Mon Sep 17 00:00:00 2001
From: Henrique Graca <999396+hjgraca@users.noreply.github.com>
Date: Wed, 24 Jul 2024 12:09:50 +0100
Subject: [PATCH] Add lambda layer policy to versioning docs

Signed-off-by: Henrique Graca <999396+hjgraca@users.noreply.github.com>
---
 docs/versioning.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/versioning.md b/docs/versioning.md
index ca092c897e8..30499d7981a 100644
--- a/docs/versioning.md
+++ b/docs/versioning.md
@@ -45,6 +45,16 @@ Powertools for AWS Lambda follows the [AWS Lambda Runtime deprecation policy cyc
 
 !!! note "AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version"
 
+### Lambda layer lifecycle
+
+Powertools for AWS Lambda provides public Lambda layers as an alternative method for including the Powertools SDK into your Lambda functions.
+
+Unlike package indexers such as PyPi and NPMJS, which use semantic versioning (e.g., v1.2.3, v1.3.0), Lambda layers employs incrementing sequential versions (e.g., 1, 2, 3, 4). With each new release of the SDK, Powertools for AWS Lambda publishes an updated layer, including the SDK version in the layer description.
+
+Powertools for AWS Lambda layers are immutable and remain available beyond their end-of-life dates.
+
+Each Powertools for AWS Lambda layer adheres to the versioning policy outlined above.
+
 ### Communication methods
 
 Maintenance announcements are communicated in several ways: