Skip to content

docs(changelog): record reference-data (#379) under 0.55.0#388

Merged
padak merged 1 commit into
mainfrom
chore/changelog-0.55.0-reference-data
Jun 4, 2026
Merged

docs(changelog): record reference-data (#379) under 0.55.0#388
padak merged 1 commit into
mainfrom
chore/changelog-0.55.0-reference-data

Conversation

@padak

@padak padak commented Jun 4, 2026

Copy link
Copy Markdown
Member

Summary

PR #379 (semantic-layer reference-data) merged without a changelog entry — the version bump + changelog were deferred to release-time per CONTRIBUTING. This adds the missing entry to the pending 0.55.0 release so it ships complete release notes alongside #383 (sync plaintext audit) and #384 (hint-subsystem removal).

Why 0.55.0 (not 0.56.0)

0.55.0 is in pyproject.toml but not yet released (latest tag/release is v0.54.0). reference-data merged into main before 0.55.0 shipped, so it rides the same train — the since v0.55.0 doc tags from #379 stay correct, no retag needed.

Changes

Verification

  • make check green (lint/format/changelog-check/skill/version + 3843 passed).

Follow-up after merge: tag v0.55.0 + GitHub release.


Open in Devin Review

PR #379 merged the semantic-layer reference-data commands without a
changelog entry (version bump deferred to release-time per CONTRIBUTING).
Add the entry to the pending 0.55.0 release alongside #383 (sync audit)
and #384 (hint removal) so 0.55.0 ships complete release notes.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@padak padak merged commit 66e17d8 into main Jun 4, 2026
5 checks passed
@padak padak deleted the chore/changelog-0.55.0-reference-data branch June 4, 2026 19:25
padak added a commit that referenced this pull request Jun 4, 2026
…livery (#399)

0.55.0 sat in main across three builds (#383, #379, #388) under one
version number, so users on an interim 0.55.0 build never received the
reference-data commands via `kbagent update` (the auto-update check is
version-only: 0.55.0 >= 0.55.0 reads as up-to-date). Bump to 0.56.0 gives
auto-update a strictly-greater target. No code changes; reference-data
stays recorded under 0.55.0 and its since-tags remain correct.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant