-
Notifications
You must be signed in to change notification settings - Fork 594
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
v3.377.0 release is broken (@smithy/hash-stream-node is not declared as a dependency) #5014
Comments
+1 facing the same issue! We are on node Downgraded to |
+1 facing same issue .. edit: i had to downgrade to version 3.360.0 for it to work.. |
@srchase @kuhe could you check if this is just a missing dependency declaration for |
Seems that in #4990 you forgot to add the |
Adding an explicit dependency on |
Hi everyone. Thanks for letting us know. All the best, |
A fix was merged in #4987, adding the missing dependency. We will include this patch in the next release, which is expected to be later today. |
v3.377.0 of
Is there anything specific to your application that would cause this transitive dependency to be missing? In any case, |
@kuhe Here is the relevant part of my dependency tree with no
Happy that this got turned around so quickly. |
Ok, looking at your tree and back at v3.377.0, I now know what happened. v3.377.0 released with an unintentionally wide version range for the dependency As a fix for this issue, you can install v3.377.0 with a fresh lockfile, or use the patched version v3.378.0. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Checkboxes for prior research
Describe the bug
Upgraded to v3.377.0 and CI is breaking in specs and smoke test container due to error in
@smithy/hash-stream-node
We are using renovate and we are upgrading on almost every release you do. So far each has worked, up until this one. We are an ESM project.
When starting server there is a more detailed error:
Section: server logs
Starting server
SDK version number
@aws-sdk/[email protected]
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v18.17.0
Reproduction Steps
Nope
Observed Behavior
Nope
Expected Behavior
Nope
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: