Skip to content

chore(release): renumber the unreleased 0.83.0 to 0.82.1 - #582

Closed
padak wants to merge 1 commit into
mainfrom
chore/renumber-0821
Closed

chore(release): renumber the unreleased 0.83.0 to 0.82.1#582
padak wants to merge 1 commit into
mainfrom
chore/renumber-0821

Conversation

@padak

@padak padak commented Aug 12, 2026

Copy link
Copy Markdown
Member

v0.82.0 shipped while #581 was in review, and it carried 0.81.0 with it via the
catch-up mechanism. That leaves exactly one unreleased change: the #581
documentation note recording that no mcp_tool migration command will be built.

A minor bump for a docs-only note is inflation -- nothing in it changes
behaviour, adds a command or moves an interface. 0.82.1 says what actually
happened.

Renumbered in pyproject.toml, the changelog key, and the (0.83.0+) since-tag
in keboola-expert.md; plugin.json / marketplace.json / uv.lock follow via
make version-sync. No content change.


Open in Devin Review

v0.82.0 shipped while #581 was in review, and it carried 0.81.0 with it via the
catch-up mechanism. That leaves exactly one unreleased change: the #581
documentation note recording that no mcp_tool migration command will be built.

A minor bump for a docs-only note is inflation -- nothing in it changes
behaviour, adds a command or moves an interface. 0.82.1 says what actually
happened.

Renumbered in pyproject.toml, the changelog key, and the `(0.83.0+)` since-tag
in keboola-expert.md; plugin.json / marketplace.json / uv.lock follow via
`make version-sync`. No content change.

@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 found 1 potential issue.

Open in Devin Review

# Ordered newest-first. Each value is a list of brief one-line descriptions.
CHANGELOG: dict[str, list[str]] = {
"0.83.0": [
"0.82.1": [

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Changelog key renumbered but the entry still describes an unreleased-only doc note

The 0.82.1 entry body still says the migration recipe lives in the skill's gotchas.md; since that gotcha was authored alongside the note in #581 it should carry a (since v0.82.1) tag rather than 0.83.0 — the search shows no stale tag, but reviewers may want to confirm the gotcha entry is version-tagged at all, since CONTRIBUTING.md makes the tag non-optional and CI does not check it.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@padak

padak commented Aug 13, 2026

Copy link
Copy Markdown
Member Author

Closing as obsolete -- the premise no longer holds.

This PR assumed 0.83.0 was the only unreleased change, and that a minor bump for
a docs-only note was inflation. Since then #565 (auth login-password) merged and
took main to 0.84.0, so there are now two unreleased changelog keys, 0.83.0 and
0.84.0, and the version files this PR rewrites are already at 0.84.0 -- hence the
conflicts.

The inflation concern is also moot: 0.83.0 will never be its own release tag.
gh release list shows the last tag is v0.82.0; 0.81.0 was carried by it via the
catch-up mechanism, and 0.83.0 will be carried by v0.84.0 the same way. Renumbering
it to 0.82.1 would only place a patch of 0.82 below an already-written 0.84.0 entry
in the changelog, which reads worse than leaving it alone.

If the empty-looking 0.83.0 key ever becomes a nuisance, the cheaper fix is to fold
its note into the 0.84.0 entry and retag the since-marker in
plugins/kbagent/agents/keboola-expert.md from (0.83.0+) to (0.84.0+) -- the
version users actually receive it in. No rebase of five version-synced files needed.

@padak padak closed this Aug 13, 2026
@padak
padak deleted the chore/renumber-0821 branch August 13, 2026 21:41
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