-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[kms] inline aws4fetch #20201
[kms] inline aws4fetch #20201
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
a786a10
to
9006f58
Compare
9006f58
to
339d6dc
Compare
339d6dc
to
14bf77b
Compare
9de21d3
to
bc75b70
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh btw, do we need to do manually pnpm deprecate
for the @mysten/kms
package?
yes, we'll need to do that, probably @Jordan-Mysten (not sure who else has access to our npm org) |
Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.