Checking in changes prior to tagging of version 0.7.0.

[shogo82148]

Changelog diff is:

diff --git a/Changes b/Changes
index 49a76a3..db60fb4 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension aws-lambda

{{$NEXT}}
+
+0.7.0 2025-12-13T04:33:18Z
- Support tenant id in AWS::Lambda::Context #203
- Add support for AWS_LAMBDA_MAX_CONCURRENCY #204
- Mark Amazon Linux 2 (AL2) based layers as no longer maintained #206

Summary by CodeRabbit

• New Features

  • Added tenant ID support in AWS::Lambda::Context
  • Added support for AWS_LAMBDA_MAX_CONCURRENCY environment variable

• Deprecations

  • Amazon Linux 2 (AL2) based layers marked as no longer maintained; migration to AL2023 recommended

• Documentation

  • Updated layer naming conventions and maintenance status guidance
  • Clarified migration path to Amazon Linux 2023

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This release PR bumps the package version from 0.6.0 to 0.7.0 across all module files and manifests. It adds release notes documenting three features: tenant ID support in Lambda context, AWS_LAMBDA_MAX_CONCURRENCY support, and marking AL2-based layers as no longer maintained. Documentation is updated to clarify AL2 deprecation and migrate references toward AL2023.

Changes

Cohort / File(s)	Summary
Version bumps META.json, lib/AWS/Lambda.pm, lib/AWS/Lambda/AL.pm, lib/AWS/Lambda/AL2.pm, lib/AWS/Lambda/AL2023.pm	Updated version from 0.6.0 to 0.7.0 in module and manifest files
Documentation updates README.md	Clarified AL2 as no longer maintained, updated AL2 → AL2023 references, fixed typo (availeble → available), adjusted layer naming guidance and ARN references
Release notes Release notes file	Added v0.7.0 changelog documenting three updates: tenant ID support, AWS_LAMBDA_MAX_CONCURRENCY support, and AL2 maintenance status

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

The changes consist primarily of homogeneous version bumps (repetitive string replacements) combined with straightforward documentation updates. The release notes are factual summaries. Primary review focus should be:

• Verification that documentation accuracy reflects the three features mentioned in release notes
• Confirmation that AL2 deprecation messaging is consistent across files

Possibly related PRs

• #206: Directly corresponds to the release v0.7.0 version bump and AL2 deprecation documentation changes
• #202: Updates AL2 → AL2023 references for Lambda layers across documentation files, matching the README changes in this PR

Poem

🐰 A version ascends from point six to seven,
AL2 rests while AL2023 climbs to heaven,
Docs align, the tenants dance free,
Concurrency flows like berries in thee! 🫐

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch prepare-for-release-v0.7.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8b28cae and 5adfffd.

📒 Files selected for processing (7)

• Changes (1 hunks)
• META.json (1 hunks)
• README.md (2 hunks)
• lib/AWS/Lambda.pm (1 hunks)
• lib/AWS/Lambda/AL.pm (1 hunks)
• lib/AWS/Lambda/AL2.pm (1 hunks)
• lib/AWS/Lambda/AL2023.pm (1 hunks)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}