Closed JoseAngel1196 closed 1 month ago
@JoseAngel1196 please see the draft PR #1041 for the current thinking around the initial aws-v1 migration. The main idea here is to leverage type aliases to maintain backwards compatibility.
@JoseAngel1196 please see the draft PR #1041 for the current thinking around the initial aws-v1 migration. The main idea here is to leverage type aliases to maintain backwards compatibility.
nice! Will wait to work on this PR until you finish there!
@JoseAngel1196 please see the draft PR #1041 for the current thinking around the initial aws-v1 migration. The main idea here is to leverage type aliases to maintain backwards compatibility.
nice! Will wait to work on this PR until you finish there!
@JoseAngel1196 #1041 has been merged now.
@JoseAngel1196 please see the draft PR #1041 for the current thinking around the initial aws-v1 migration. The main idea here is to leverage type aliases to maintain backwards compatibility.
nice! Will wait to work on this PR until you finish there!
@JoseAngel1196 #1041 has been merged now.
Sounds good, going to be working on this week.
To help us get this pull request reviewed and merged quickly, please be sure to include the following items:
PR Type
What kind of change does this PR introduce?
Backward Compatibility
Is this change backward compatible with the most recently released version? Does it introduce changes which might change the user experience in any way? Does it alter the API in any way?
Issue Linking
What's new?
-