Skip to content

release(jetbrains): v7.0.14 - #12964

Closed
kirillk wants to merge 3 commits into
mainfrom
jetbrains/release/v7.0.14
Closed

release(jetbrains): v7.0.14#12964
kirillk wants to merge 3 commits into
mainfrom
jetbrains/release/v7.0.14

Conversation

@kirillk

@kirillk kirillk commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Prepare JetBrains stable release 7.0.14.
  • Review packages/kilo-jetbrains/gradle.properties and edit packages/kilo-jetbrains/CHANGELOG.md before merging.

JetBrains-Version: 7.0.14
JetBrains-Kind: stable
JetBrains-From-Tag: jetbrains/v7.0.13
JetBrains-Tag: jetbrains/v7.0.14
JetBrains-Commit: 978c44f

Generated Notes

What's Changed

Full Changelog: jetbrains/v7.0.13...jetbrains/v7.0.14

@kirillk kirillk added the jetbrains-release Required gate for JetBrains release publishing label Aug 6, 2026

## [Unreleased]

## [7.0.14] - 2026-08-06

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

WARNING: The 7.0.14 entry is still the raw generated "What's Changed" notes, not the curated human-readable changelog this release process expects.

The PR description says to edit CHANGELOG.md before merging, and every prior release got that edit: v7.0.13's generated notes were rewritten into prose in 656afef284 (docs(jetbrains): edit changelog for v7.0.13), same for v7.0.12 in 12a29f5f37. Compared to the curated [7.0.13] / [7.0.12] entries below, this one still has:

  • Conventional-commit prefixes (feat(vscode):, fix(cli):) instead of user-facing prose
  • by @user in https://github.com/.../pull/NNNNN attribution noise on every line
  • A self-referential release(jetbrains): v7.0.13 by @kilo-maintainer[bot] item under ### Changed (and a docs: item) that a filtered changelog would drop

This text ships to users via the JetBrains Marketplace plugin page, so worth the curation pass (e.g. a docs(jetbrains): edit changelog for v7.0.14 commit) before this merges.


Reply with @kilocode-bot fix it to have Kilo Code address this issue.

@kilo-code-bot

kilo-code-bot Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Previous finding resolved: the 7.0.14 changelog entry is now curated into user-facing release notes.

Files Reviewed (2 files)
  • packages/kilo-jetbrains/CHANGELOG.md - 7.0.14 entry curated; both bullets match the release notes (slash command matching, CLI database lock crash fix)
  • packages/kilo-jetbrains/gradle.properties - version bump 7.0.13 → 7.0.14, unchanged since previous review
Previous Review Summary (commit 2292fe8)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 2292fe8)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 0
Issue Details (click to expand)

WARNING

File Line Issue
packages/kilo-jetbrains/CHANGELOG.md 131 7.0.14 entry is still raw generated notes; prior releases got a curated docs(jetbrains): edit changelog rewrite before merge (PR body also asks for this edit). Includes self-referential release(jetbrains): v7.0.13 noise under Changed.
Files Reviewed (2 files)
  • packages/kilo-jetbrains/gradle.properties - version bump 7.0.13 → 7.0.14, kilo.cli.pinned=true intact, no issues
  • packages/kilo-jetbrains/CHANGELOG.md - 1 issue (uncurated generated notes); all 27 PRs from the release notes are present, no duplicates

Fix these issues in Kilo Cloud


Reviewed by kimi-k3 · Input: 108K · Output: 3.3K · Cached: 195.6K

Review guidance: REVIEW.md from base branch main

@kirillk kirillk closed this Aug 7, 2026
@kirillk
kirillk deleted the jetbrains/release/v7.0.14 branch August 7, 2026 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jetbrains-release Required gate for JetBrains release publishing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant