Skip to content

docs: add release-note fragment for PR #2092#2127

Closed
llm-d-router-release-notes[bot] wants to merge 1 commit into
mainfrom
release-notes/pr-2092
Closed

docs: add release-note fragment for PR #2092#2127
llm-d-router-release-notes[bot] wants to merge 1 commit into
mainfrom
release-notes/pr-2092

Conversation

@llm-d-router-release-notes

Copy link
Copy Markdown
Contributor

Stages release-note fragment for #2092. Will be assembled into RELEASE-NOTES.md at the next release tag.

Signed-off-by: llm-d-router-release-notes[bot] <287676111+llm-d-router-release-notes[bot]@users.noreply.github.com>
@llm-d-router-release-notes
llm-d-router-release-notes Bot requested a review from a team as a code owner July 21, 2026 23:13
@github-actions github-actions Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 21, 2026

@elevran elevran left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@LukeAVanDrie -
this is an internal bug fix. IMO, and does not need an explicit user facing message. Note that releases reference all merged PRs so it would be visible still without the release note.
I'm in favor of closing without merge but open to the alternative. WDYT?

@LukeAVanDrie

Copy link
Copy Markdown
Contributor

I think it's fine to close this without merge. Will keep this in mind for future PRs, thanks for the feedback!

@LukeAVanDrie

Copy link
Copy Markdown
Contributor

closing per @elevran's suggestion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants