Skip to content

docs: assemble release notes for v0.9.1#1700

Open
llm-d-router-release-notes[bot] wants to merge 4 commits into
mainfrom
release-notes/assemble-v0.9.1
Open

docs: assemble release notes for v0.9.1#1700
llm-d-router-release-notes[bot] wants to merge 4 commits into
mainfrom
release-notes/assemble-v0.9.1

Conversation

@llm-d-router-release-notes

@llm-d-router-release-notes llm-d-router-release-notes Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Assembles staged release-note fragments into RELEASE-NOTES.md for v0.9.1 and removes the fragments.

liu-cong and others added 4 commits June 16, 2026 13:10
@liu-cong
release: set LATENCY_PREDICTOR_TAG to v0.8.0-rc.1
181aa83 
Signed-off-by: Cong Liu <conliu@google.com>
@vMaroon @liu-cong
deps(go): bump llm-d-kv-cache to v0.9.0 (#1691)
d528f18 
Update github.com/llm-d/llm-d-kv-cache from v0.9.0-rc.1 to the
released v0.9.0.

Signed-off-by: Maroon Ayoub <mayoub@redhat.com>
Signed-off-by: Cong Liu <conliu@google.com>
@weizhoublue @liu-cong
fix(chart): update latency predictor image path to match subchart nes…
f95e36b 
…ting (#1683)

Signed-off-by: weizhoublue <weizhou.lan@daocloud.io>
Signed-off-by: Cong Liu <conliu@google.com>
@llm-d-router-release-notes
docs: assemble release notes for v0.9.1
30d1c08 
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 June 22, 2026 01:54
@github-actions github-actions Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 22, 2026
@ahg-g

ahg-g commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

@liu-cong @elevran is this PR expected to merge or should it be closed?

@liu-cong

liu-cong commented Jun 22, 2026

Copy link
Copy Markdown
Member

@elevran The release note consolidation makes sense. But should we also pull in other commits from the release branch? For example, the latency predictor image version is only supposed to be made on the release branch.

@elevran

elevran commented Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

the idea is that the consolidated file is appended to on every release and the fragments are then deleted.

  • can possibly avoid for release candidates (-rc*) so the consolidate file is for "real" releases only. This requires a change in the action (shouldn't be too hard).
  • when you create the GH release, it already has the option to list all commits. This is a summary of what went it - dev and user focused alike. The release notes files is user facing only and relies on the block in PR description.
  • relevant items from commits can be added to the release notes file if/when they have bearing on user facing aspects (eg., latency prediction image update). How would you automatically find these, esp. when due to PRs in other repos? If PRs in our repo, should request a release notes block in the PR body

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

Reviewers

@ahg-g ahg-g Awaiting requested review from ahg-g ahg-g is a code owner automatically assigned from llm-d/router-maintainers

@vMaroon vMaroon Awaiting requested review from vMaroon vMaroon is a code owner automatically assigned from llm-d/router-maintainers

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@ahg-g @liu-cong @elevran @vMaroon @weizhoublue