feat(general): amended all lambda runtime deprecations thru Jun 30 2026

Open RoryKiefer opened this issue 6 months ago • 5 comments

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

Aug 25 '25 18:08 RoryKiefer

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

Sep 21 '25 12:09 maxamel

@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!

Oct 22 '25 21:10 RoryKiefer

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

Oct 31 '25 10:10 maxamel

hi @RoryKiefer , in the recent commit I found some csv files that seem unnecessary. Can you elaborate why they are needed in this PR ?

Nov 19 '25 07:11 maxamel

@maxamel not sure where those CSV files came from -- perhaps an artifact of the tests I ran? Either way, they've been cleaned up.

Dec 03 '25 21:12 RoryKiefer

@maxamel python 3.9 runtime is deprecated today. Firing up a code change!

Dec 15 '25 15:12 RoryKiefer

@maxamel not sure where those CSV files came from -- perhaps an artifact of the tests I ran? Either way, they've been cleaned up.

@RoryKiefer I see they are still there. Can you re-check?

Dec 18 '25 07:12 maxamel