chore(release): log #560, #568, #569 and #584 under 0.84.0 - #590
Conversation
0.84.0 is still untagged, so the three changes riding this catch-up release go under the existing key rather than claiming a version of their own -- 0.85.0 is reserved for the epic #390 removal. Covers the promotion-pipeline skill (#560), the lineage ambiguity warning (#568) and the case-insensitive config-based search (#569).
| "New: a `kbagent-promotion-pipeline` skill that generates a from-scratch GitHub " | ||
| "Actions setup promoting configurations from a SOURCE project (dev) to a " | ||
| "DESTINATION project (prod), with a human-reviewed PR gate in between. `sync` " |
There was a problem hiding this comment.
🟡 New release note's one-line summary gets cut off mid-sentence
The new promotion-pipeline release note opens with a sentence far longer than the summary width (src/keboola_agent_cli/changelog.py:43-45), so the default one-line view renders it as "... promoting configurations from a SOURCE project (dev) to a …" -- the cut lands before the point of the change.
Impact: Anyone reading the release notes (or the post-update "What's new" banner) sees a truncated, incomplete description of the new skill instead of a self-contained summary.
Headline extraction and the 160-character cap
The authoring contract in this file's docstring (src/keboola_agent_cli/changelog.py:15-16) and CONTRIBUTING step 2 of "Releasing a new version" require each bullet to "lead with a self-contained first sentence" because that sentence becomes the default summary. headline() (src/keboola_agent_cli/changelog.py:2057-2081) takes the first sentence and truncates it to CHANGELOG_HEADLINE_MAX_CHARS = 160 (src/keboola_agent_cli/constants.py:492). Rendering the new entry yields 152 characters ending in "to a …", i.e. the PR gate / destination half of the sentence -- the actual value of the change -- is dropped in kbagent changelog (non---full) and in format_whats_new().
Prompt for agents
The new 0.84.0 bullet for the promotion-pipeline skill opens with a sentence longer than 160 characters, so headline() truncates it mid-clause ("... from a SOURCE project (dev) to a …") in the default `kbagent changelog` view and in the post-update "What's new" banner. The changelog authoring contract (module docstring, plus CONTRIBUTING "Releasing a new version" step 2) requires the first sentence to be self-contained because it becomes the summary. Rewrite the bullet so its first sentence fits within CHANGELOG_HEADLINE_MAX_CHARS (160) while still naming the skill and what it does end-to-end (e.g. a short "New (#560): a `kbagent-promotion-pipeline` skill that scaffolds a PR-gated dev -> prod promotion pipeline in GitHub Actions." followed by the current detail as subsequent sentences). Verify with `headline()` that the result is not truncated.
Was this helpful? React with 👍 or 👎 to provide feedback.
Changelog entries for everything riding the 0.84.0 catch-up release. No code change.
0.84.0is still untagged -- the last release isv0.82.0, and0.83.0/0.84.0are sitting on main unreleased -- so these go under the existing key rather than claiming a version of their own.0.85.0stays reserved for the epic #390 removal.Covers:
PROJECT:rather than an angle-bracket placeholder--regexis rejected on that surface so there was no workaroundmake changelog-checkand lint pass.