Skip to content

Conversation

@keelerm84
Copy link
Member

No description provided.

@keelerm84 keelerm84 requested a review from a team as a code owner November 4, 2025 14:44
@keelerm84 keelerm84 changed the title feat: Provide HTTP headers via Start event feat: Provide access to HTTP headers on success or error Nov 4, 2025
Comment on lines 129 to 130
For HTTP-based connections, this contains the headers from the SSE response.
For non-HTTP connections, this will be ``None``.
Copy link
Member

Choose a reason for hiding this comment

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

Do we need this section? I am always hesitant of "non-HTTP" SSE as a concept. But above we already say "if available", so we know it is optional.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll remove it.

@keelerm84 keelerm84 merged commit b83f356 into main Nov 7, 2025
13 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-1538/expose-headers branch November 7, 2025 18:41
keelerm84 pushed a commit that referenced this pull request Nov 7, 2025
🤖 I have created a release *beep* *boop*
---


##
[1.5.0](1.4.0...1.5.0)
(2025-11-07)


### Features

* Provide access to HTTP headers on success or error
([#53](#53))
([b83f356](b83f356))

---
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>
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