Skip to content
New issue

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

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

Already on GitHub? # to your account

fix: dont set _contentLength if not in headers #368

Merged
merged 1 commit into from
May 6, 2024

Conversation

lukekarrys
Copy link
Contributor

The opposite of #366. This is not a change in behavior but makes it clear that we don't expect _contentLength to be set when the request is coming directly from the registry when there is no cache.

The opposite of #366. This is not a change in behavior but makes it clear that we don't expect _contentLength to be set when the request is coming directly from the registry when there is no cache.
@lukekarrys lukekarrys requested a review from a team as a code owner May 6, 2024 17:44
@lukekarrys lukekarrys merged commit 5e75582 into main May 6, 2024
17 checks passed
@lukekarrys lukekarrys deleted the lk/no-content-length branch May 6, 2024 17:51
@github-actions github-actions bot mentioned this pull request May 6, 2024
lukekarrys pushed a commit that referenced this pull request May 6, 2024
🤖 I have created a release *beep* *boop*
---


## [18.0.5](v18.0.4...v18.0.5)
(2024-05-06)

### Bug Fixes

*
[`5e75582`](5e75582)
[#368](#368) dont set _contentLength
if not in headers (#368) (@lukekarrys)
*
[`1b6950b`](1b6950b)
[#365](#365) move bin to its own
directory (@lukekarrys)
*
[`1b6950b`](1b6950b)
[#365](#365) refactor: symbol cleanup
(#365) (@lukekarrys)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants