Release packages#1211
Conversation
knope-bot
Bot
requested review from
1egoman,
MaxHeimbrock,
alan-george-lk,
ladvoc,
lukasIO,
stephen-derosa and
xianshijing-lk
as code owners
ChangesetChangeset found but no version bumps declared. |
knope-bot
Bot
force-pushed
the
knope/release
branch
2 times, most recently
from
00a7b7b to
d667a69
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| ## 0.12.69 (2026-07-06) | ||
|
|
||
| ### Fixes | ||
|
|
||
| - feat: auto failover APIs with LK Cloud - #1196 (@davidzhao) | ||
| - Turn single peerconnection off by default - #1206 (@cnderrauber) | ||
|
|
There was a problem hiding this comment.
🟡 Latest release notes are buried in the middle of the changelog instead of appearing at the top
The newest version entry is inserted between old entries rather than at the top of the file (livekit-ffi/CHANGELOG.md:319), so readers looking for the latest release notes will not find them in the expected position.
Impact: Anyone reading the changelog will see outdated entries first and may miss the latest release notes entirely.
Changelog entry inserted at wrong position in the file
The livekit-ffi/CHANGELOG.md file has two sections of entries: old-format entries at the top (lines 10-318, versions [0.12.47] down to [0.12.3]) and new-format entries below (versions 0.12.68 down to 0.12.60). The new 0.12.69 entry was appended at the junction between these two sections (line 319), right after the [0.12.3] entry from 2024-12-14, instead of being placed after ## [Unreleased] at line 8.
Additionally, there is a missing blank line before the ## 0.12.69 heading — it directly follows the previous section's last bullet point (- bump libwebrtc to m125 at line 318), which breaks markdown rendering by merging the heading into the previous list.
The correct placement would be between ## [Unreleased] (line 8) and ## [0.12.47] (line 10), consistent with how livekit-api/CHANGELOG.md was updated.
Prompt for agents
The new changelog entry for version 0.12.69 in livekit-ffi/CHANGELOG.md was inserted at line 319 (between the old [0.12.3] entry and the 0.12.68 entry) instead of at the top of the changelog after the ## [Unreleased] section (line 8). The entry needs to be moved from its current position (lines 319-325) to after line 9 (the blank line following ## [Unreleased]). A blank line also needs to be added before the ## 0.12.69 heading since it currently runs directly into the previous bullet point. Compare with livekit-api/CHANGELOG.md which has the correct placement.
Was this helpful? React with 👍 or 👎 to provide feedback.
| ## 0.7.51 (2026-07-06) | ||
|
|
||
| ### Fixes | ||
|
|
||
| - feat: auto failover APIs with LK Cloud - #1196 (@davidzhao) | ||
| - Turn single peerconnection off by default - #1206 (@cnderrauber) | ||
|
|
There was a problem hiding this comment.
🟡 Latest release notes are buried in the middle of the changelog instead of appearing at the top
The newest version entry is inserted between old entries rather than at the top of the file (livekit/CHANGELOG.md:260), so readers looking for the latest release notes will not find them in the expected position.
Impact: Anyone reading the changelog will see outdated entries first and may miss the latest release notes entirely.
Changelog entry inserted at wrong position in the file
The livekit/CHANGELOG.md file has two sections of entries: old-format entries at the top (lines 10-259, versions [0.7.32] down to [0.7.1]) and new-format entries below (versions 0.7.50 down to 0.7.42). The new 0.7.51 entry was appended at the junction between these two sections (line 260), right after the [0.7.1] entry from 2024-12-14, instead of being placed after ## [Unreleased] at line 8.
Additionally, there is a missing blank line before the ## 0.7.51 heading — it directly follows the previous section's last bullet point (- bump libwebrtc to m125 at line 259), which breaks markdown rendering by merging the heading into the previous list.
The correct placement would be between ## [Unreleased] (line 8) and ## [0.7.32] (line 10), consistent with how livekit-api/CHANGELOG.md was updated.
Prompt for agents
The new changelog entry for version 0.7.51 in livekit/CHANGELOG.md was inserted at line 260 (between the old [0.7.1] entry and the 0.7.50 entry) instead of at the top of the changelog after the ## [Unreleased] section (line 8). The entry needs to be moved from its current position (lines 260-266) to after line 9 (the blank line following ## [Unreleased]). A blank line also needs to be added before the ## 0.7.51 heading since it currently runs directly into the previous bullet point. Compare with livekit-api/CHANGELOG.md which has the correct placement.
Was this helpful? React with 👍 or 👎 to provide feedback.
| ### Fixes | ||
|
|
||
| - feat: auto failover APIs with LK Cloud - #1196 (@davidzhao) | ||
| - Turn single peerconnection off by default - #1206 (@cnderrauber) |
There was a problem hiding this comment.
🔍 Feature listed under "Fixes" heading in changelog entries
In both livekit-ffi/CHANGELOG.md:323 and livekit/CHANGELOG.md:264, the entry "feat: auto failover APIs with LK Cloud" is listed under a ### Fixes heading. This is a feature, not a fix, as indicated by the feat: prefix. The changeset file .changeset/feat_auto_failover_apis_with_lk_cloud.md also describes it as a feature. The livekit-api/CHANGELOG.md:14 correctly places this under ### Features. This appears to be a knope tooling issue where the section heading was generated incorrectly for these two crates.
Was this helpful? React with 👍 or 👎 to provide feedback.
knope-bot
Bot
force-pushed
the
knope/release
branch
from
d667a69 to
b38e821
Compare
There was a problem hiding this comment.
🔍 Changelog insertion issue likely caused by knope tooling encountering split changelog formats
The livekit-ffi/CHANGELOG.md and livekit/CHANGELOG.md files have a split structure: older entries use the release-plz format with bracketed links (e.g., ## [0.12.47](...)), while newer entries use the knope format (e.g., ## 0.12.68 (2026-06-30)). The knope-format entries were previously appended at the end of the file (after the oldest release-plz entries). This release appears to have appended the new entry at the same boundary, resulting in the new 0.12.69/0.7.51 entries appearing between the oldest release-plz entry and the existing knope entries. The livekit-api/CHANGELOG.md and livekit-uniffi/CHANGELOG.md don't have this split structure, which is why they were generated correctly. This suggests the release tooling may need adjustment to handle the mixed-format changelogs.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
|
||
| - feat: auto failover APIs with LK Cloud - #1196 (@davidzhao) | ||
| - Fix for dynacast error - #1213 (@MaxHeimbrock) | ||
| - Turn single peerconnection off by default - #1206 (@cnderrauber) |
There was a problem hiding this comment.
🟡 Changelog entry describes the opposite of what the code change actually does
The release notes say the feature is turned "off" by default (livekit/CHANGELOG.md:266), but the actual code change sets single_peer_connection from false to true, so the feature is turned on.
Impact: Users reading the changelog will believe single peer connection is disabled when it is actually enabled, potentially causing confusion when debugging connection behavior.
Mismatch between changeset description and code
Commit 95187df ("Turn single peerconnection on by default (#1206)") changes single_peer_connection: false to single_peer_connection: true in livekit/src/room/mod.rs:437. However, the changeset file .changeset/turn_single_peerconnection_off_by_default.md (now deleted) described this as "Turn single peerconnection off by default". This incorrect description was propagated into the changelogs for both livekit/CHANGELOG.md:266 and livekit-ffi/CHANGELOG.md:325.
Was this helpful? React with 👍 or 👎 to provide feedback.
knope-bot
Bot
force-pushed
the
knope/release
branch
from
b38e821 to
0cb3a89
Compare
Important
Merging this pull request will create these releases
livekit 0.7.51 (2026-07-07)
Fixes
livekit-ffi 0.12.69 (2026-07-07)
Fixes
livekit-uniffi 0.1.4 (2026-07-07)
Features
livekit-api 0.5.5 (2026-07-07)
Features
livekit-datatrack 0.1.10 (2026-07-07)
Fixes
libwebrtc 0.3.40 (2026-07-07)
Fixes