Repository navigation
release(jetbrains): v7.1.7 - #14509
Conversation
kilo-maintainer
Bot
added
the
jetbrains-release
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| - feat(cli): add experimental self-context tools by @iscekic in https://github.com/Kilo-Org/kilocode/pull/14268 | ||
| - feat(cli): add background process monitor and session cron scheduling by @iscekic in https://github.com/Kilo-Org/kilocode/pull/14312 | ||
| - feat(cli): link sessions to pull requests via tool and remote check by @iscekic in https://github.com/Kilo-Org/kilocode/pull/14315 | ||
| - feat(ci): sign Windows CLI binaries with Azure Key Vault EV certificate by @zfralish in https://github.com/Kilo-Org/kilocode/pull/13981 |
There was a problem hiding this comment.
SUGGESTION: Reverted feature listed under ### Added
PR #13981 (feat(ci): sign Windows CLI binaries with Azure Key Vault EV certificate) was reverted by #14461 before this release, so it never shipped in 7.1.7. Keeping it under ### Added would advertise a feature that does not exist. Suggest dropping this line while editing the changelog.
More broadly, this [7.1.7] block is still the raw generated notes rather than the filtered, user-facing changelog the release process expects (packages/kilo-jetbrains/RELEASING.md:110; release-jetbrains skill). VS Code/docs/CI-only entries such as this one, fix(ci): ..., docs(kilo-docs): ..., and refactor(vscode): ... should be dropped or rewritten before merge, since the reviewed changelog is what gets rendered into JetBrains <change-notes>.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous Review Summary (commit da0ac71)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit da0ac71)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (2 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
|
|
||
| ### Fixed | ||
|
|
||
| - Pause the working timer while waiting on a permission prompt or a question. |
There was a problem hiding this comment.
SUGGESTION: A few shipped 7.1.7-rc.* changes are missing from the aggregated [7.1.7] notes
While condensing the generated notes into user-facing entries, some changes from the RC sections were dropped from the stable section. The stable section is what gets rendered into the Marketplace <change-notes>, so these will not appear on the 7.1.7 release page:
[7.1.7-rc.5]: "Deliver plan completion questions to directory-scoped clients such as JetBrains without requiring a reconnect." - explicitly JetBrains-facing.[7.1.7-rc.2]: "Clear stopped session status before publishing status events, so reload no longer stays blocked by a session that already finished."[7.1.7-rc.3](Added): "Show scheduled/progress polish for session actions with a shimmering progress footer."
Consider restoring the user-visible ones (at least the plan completion fix) so the 7.1.7 notes stay complete.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
kwf-read-edit |
1 similar comment
|
kwf-read-edit |
Summary
packages/kilo-jetbrains/gradle.propertiesand editpackages/kilo-jetbrains/CHANGELOG.mdbefore merging.JetBrains-Version: 7.1.7
JetBrains-Kind: stable
JetBrains-From-Tag: jetbrains/v7.1.6
JetBrains-Tag: jetbrains/v7.1.7
JetBrains-Commit: bed1358
Generated Notes
What's Changed
llms.txt, no redirects) #13972 — fix(docs): add redirects for legacy paths and root llms.txt by @emilieschario in Closes #13972 — fix(docs): add redirects for legacy paths and root llms.txt #14171New Contributors
Full Changelog: jetbrains/v7.1.6...jetbrains/v7.1.7