release 0.71.0: changelog backfill + alignment version bump#499
Merged
Conversation
Ten PRs merged since v0.66.1 carried no changelog entry because they did not bump the version, so 'kbagent changelog' and the post-update What's new display would silently omit them. Attributed to the version whose bump window they were merged in: - 0.67.0: #465 (plaintext_written --json field), #490 (error-codes.md complete + check-error-codes gate) - 0.70.0: #486 (semantic-layer numeric/temporal role classification) - 0.70.1: #487 (alias/linked-bucket column-type resolution), #488 (one metric per measure field), #482/#494 (sync push dev-branch duplicates), #492 (cloud-provider error code in upload failures), #495 (Rich markup escaping in names), #493 (SKILL.md 1024-char cap) Dependency-only #489 (mcp 1.28.0 -> 1.28.1) intentionally left out.
0.67.0-0.70.1 were merged to main but never tagged or published, so auto-update users are still on 0.66.1. 0.71.0 is the catch-up release that ships all of it in one update. Changelog entry documents the alignment; per-version entries stay attributed to their bump windows.
…-release-8d949d # Conflicts: # src/keboola_agent_cli/changelog.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Preparing the v0.71.0 alignment release — the first published release since v0.66.1 (and the first with release notes since v0.66.0). Versions 0.67.0–0.70.1 were merged to main with changelog entries but never tagged or published, so auto-update users are still on 0.66.1.
On top of that, ten PRs merged in that span carried no changelog entry because they did not bump the version —
kbagent changelogand the post-update "What's new" display would silently omit them.What
1. Changelog backfill (
src/keboola_agent_cli/changelog.py), attributing each PR to the version whose bump window it was merged in:plaintext_written--json field, GHSA-7jrf follow-up), #490 (error-codes.md 46→66 +make check-error-codes)Dependency-only #489 (mcp 1.28.0 → 1.28.1) intentionally left out of the changelog; it will be mentioned in the GitHub release notes.
2. Version bump 0.70.1 → 0.71.0 (pyproject.toml +
make version-sync: plugin.json, marketplace.json, uv.lock) with a0.71.0changelog entry documenting the alignment. Per-version entries stay attributed to their original bump windows, so the What's-new display renders the full 0.67.0→0.71.0 story for users updating from 0.66.x.The v0.71.0 tag + GitHub Release (notes covering everything since v0.66.0) follow once this merges.
Verification
pytest tests/test_changelog_check.py tests/test_changelog_render.py— 23 passedpython scripts/generate_changelog.py --check— all published stable releases coveredpython scripts/sync_version.py --check— versions consistentruff check+ruff format --checkclean