Skip to content

Conversation

@RoryKiefer
Copy link

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Updating Deprecation Information in Code Commentary

Description

There are no actual code changes here, just updated dates/lines inside of pre-existing commentary. Data source

Fixes # 7283

@maxamel
Copy link
Contributor

maxamel commented Sep 21, 2025

Can you uncomment any needed versions so we can move forward with this PR ?

@RoryKiefer
Copy link
Author

RoryKiefer commented Oct 22, 2025

@maxamel sorry, I just now got back to this and performed the merger as requested.

I also noticed a bug in the implementation: I noticed "python3.9" was already deprecated in main and "python3.8" was not. It should be the other way around, with 3.8 already deprecated, and 3.9 becoming deprecated later this year in december. All of this is corrected in my branch. Another bug I fixed was "nodejs18.x" not being deprecated yet, though it currently is as of 2025/09/01, and that too is fixed in this branch.

Thanks in advance!

@maxamel maxamel deployed to scan-security October 31, 2025 10:16 — with GitHub Actions Active
@maxamel maxamel changed the title amended all lambda runtime deprecations thru Jun 30 2026 feat(general): amended all lambda runtime deprecations thru Jun 30 2026 Oct 31, 2025
@maxamel
Copy link
Contributor

maxamel commented Oct 31, 2025

Thanks @RoryKiefer, I merged from latest and re-ran all pipelines, can you fix the failures ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants