fix(middleware-expect-continue): Remove debug logging in packages/middleware-expect-continue/src/index.ts

[derekwolpert]

Issue

None associated with this issue

Description

Looks like the latest release of the @aws-sdk/middleware-expect-continue package (v3.916.0) accidentally left a debug console.log statement within its changes. Any possibility to get this PR merged, and a new release cut? As-is, this debug logging is polluting the stdout of a handful of my projects (and I imagine a bunch of other people are impacted by this as well).

aws-sdk-js-v3/packages/middleware-expect-continue/src/index.ts

Lines 39 to 43 in 1dc88bc

	console.log({
	sendHeader,
	bodyLength,
	threshold: options.expectContinueHeader,
	});

Appears the debug logging was added in: #7450

Testing

None

Additional context

None

Checklist

• If the PR is a feature, add integration tests (*.integ.spec.ts).
• If you wrote E2E tests, are they resilient to concurrent I/O?
• If adding new public functions, did you add the @public tag and enable doc generation on the package?

---

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

[kuhe]

Thanks for fixing this. I'm going to deprecate the affected version on NPM once the new version is released.

The expected time of the next release is later today.

[derekwolpert]

Thanks @kuhe, much appreciated 🙏

[kuhe]

The fix was released in https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.917.0

https://www.npmjs.com/package/@aws-sdk/middleware-expect-continue/v/3.917.0

v3.916.0 has been deprecated with message:

@aws-sdk/middleware-expect-continue v3.916.0 contains an accidental console.log statement (#7454), please upgrade to v3.917.0+

Since people are most likely not using this package directly, the way to upgrade is to install the latest version of @aws-sdk/client-s3.

https://www.npmjs.com/package/@aws-sdk/client-s3/v/3.917.0

[github-actions]

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.