Skip to content

Conversation

@didier-danloy
Copy link
Contributor

Python 3.9 has been discontinued and following an internal IcM and code change, this function code now support Python 3.12

Python 3.9 has been discontinued and following an internal IcM and code change, this function code now support Python 3.12
@prmerger-automator
Copy link
Contributor

@didier-danloy : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit d0bb268:

✅ Validation status: passed

File Status Preview URL Details
articles/sentinel/connect-aws.md ✅Succeeded

For more details, please refer to the build report.

@batamig batamig removed their assignment Nov 30, 2025
@ttorble ttorble requested a review from Copilot December 1, 2025 15:58
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the documentation to reflect the upgrade of the AWS Lambda function runtime from Python 3.9 to Python 3.12, following the discontinuation of Python 3.9 support and corresponding code updates.

  • Updated runtime version references from Python 3.9 to Python 3.12 in the AWS connector documentation

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ttorble
Copy link
Contributor

ttorble commented Dec 1, 2025

@didier-danloy This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. I'll leave this PR open in case @batamig wants to review it here. If you decide to open a new PR in the private repo, please close this PR. Thanks.

@batamig

Can you review the proposed changes? If you are no longer the author, can you reassign this PR and create a PR in the private repo to update the author metadata?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants