Skip to content

Commit 84192bb

Browse files
hjgracadreamorosi
andauthored
chore(docs): Add lambda layer policy to versioning docs (#2824)
Co-authored-by: Andrea Amorosi <[email protected]>
1 parent 72803e2 commit 84192bb

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

docs/versioning.md

+10
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,16 @@ Powertools for AWS Lambda follows the [AWS Lambda Runtime deprecation policy cyc
4545

4646
!!! note "AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version"
4747

48+
### Lambda layer lifecycle
49+
50+
Powertools for AWS Lambda provides public Lambda layers as an alternative method for including the Powertools SDK into your Lambda functions.
51+
52+
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.
53+
54+
Powertools for AWS Lambda layers are immutable and remain available beyond their end-of-life dates.
55+
56+
Each Powertools for AWS Lambda layer adheres to the versioning policy outlined above.
57+
4858
### Communication methods
4959

5060
Maintenance announcements are communicated in several ways:

0 commit comments

Comments
 (0)