Skip to content

chore(docs): Add lambda layer policy to versioning docs #2824

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 24, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/versioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading