Repository navigation
Conversation
Signed-off-by: Brenden Hogan <hoganbr@amazon.com>
Match.id is derived from the match repr, which embeds the message, so the Id hashes had to be regenerated alongside the updated messages. Signed-off-by: Kevin DeJong <kddejong@amazon.com>
kddejong
force-pushed
the
fix/lambda-runtime-lifecycle-dates
branch
from
October 27, 2026 18:18
dd57c44 to
6d7f090
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4943 +/- ##
=======================================
Coverage 94.68% 94.68%
=======================================
Files 441 441
Lines 16058 16058
Branches 3114 3114
=======================================
Hits 15204 15204
Misses 470 470
Partials 384 384
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available: Fixes #4888
Description of changes:
Updates
LmbdRuntimeLifecycle.jsonto match the current Lambda runtimes page. After this change every runtime in the file has the same deprecation, block-create and block-update dates as the page.dotnet6,dotnet8,nodejs16.x,nodejs18.x,nodejs20.x,nodejs22.x,provided.al2,python3.8,python3.9,python3.10,ruby3.2,ruby3.3: block create2027-07-29, block update2027-08-31java8.al2,java11,java17,python3.11: block create2027-07-31->2027-07-29go1.x,java8,nodejs14.x,provided,python3.7,ruby2.7: block update2027-03-03->2027-08-31java8.al2023,java11.al2023,java17.al2023(successorjava25)nodejs26.xandpython3.15(preview, nothing scheduled) anddotnet5.0/dotnet7(container only, no block dates) are left out because none of the three rules would report on them.Unit tests and quickstart snapshots are updated for the new dates. With the issue's reproduction template, W2531 now prints
2027-07-29/2027-08-31, E2531 first reports on 2027-07-29 and E2533 on 2027-08-31.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.