Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump TypeScript to ~5.2.x in smithy JS packages #1275

Merged
merged 2 commits into from
May 10, 2024
Merged

Bump TypeScript to ~5.2.x in smithy JS packages #1275

merged 2 commits into from
May 10, 2024

Conversation

trivikr
Copy link
Contributor

@trivikr trivikr commented May 10, 2024

Issue #, if available:

TypeScript releases:

We can't upgrade to 5.3+ since browser tests written using karma fail #1263 (comment)

Description of changes:

Bump TypeScript to ~5.2.x in smithy JS packages


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@trivikr trivikr requested review from a team as code owners May 10, 2024 16:33
@trivikr trivikr requested a review from hpmellema May 10, 2024 16:33
@@ -10867,6 +10867,16 @@ __metadata:
languageName: node
linkType: hard

"typescript@npm:~5.2.2":
Copy link
Contributor

Choose a reason for hiding this comment

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

no removal of the older version in lockfile?

Copy link
Contributor Author

@trivikr trivikr May 10, 2024

Choose a reason for hiding this comment

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

No. Since TypeScript versions are not updated in SSDK libs in this PR.

@trivikr trivikr merged commit 620e39b into main May 10, 2024
10 checks passed
@trivikr trivikr deleted the bump-ts-5.2 branch May 10, 2024 20:11
kuhe pushed a commit to kuhe/smithy-typescript that referenced this pull request May 28, 2024
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.

3 participants