Skip to content

chore(release): 0.95.0 - #774

Closed
martinsifra wants to merge 1 commit into
mainfrom
release/0.95.0
Closed

martinsifra wants to merge 1 commit into
mainfrom
release/0.95.0

Conversation

@martinsifra

@martinsifra martinsifra commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

Release PR for 0.95.0 — batches everything merged since v0.94.0.

Rebased onto main now that #773 has landed. make check exit 0 (6798 passed, 12 skipped), make vnext-check — all 355 gates resolve.

Scope — the three PRs the tag will contain

PR
#772 feat(auth): "press c to copy" for the device-login link
#768 chore(deps): drop pip-audit, gate CI on uv audit, require uv >= 0.12.15 (CLI-16)
#773 fix(test): un-red main — type-clean and machine-independent _url_copy tests

git log v0.94.0..main confirms nothing else.

Checklist

  • 2. pyproject.toml → 0.95.0 (minor: feat(auth): add "press c to copy" for the device-login link #772 is a feat)
  • 3. One changelog entry, three bullets, every headline under the 160-char cap (146 / 150 / 53). fix(test): make the _url_copy tests type-clean and machine-independent #773 is batched as a housekeeping Note, matching how 0.94.0 covered its chore PRs
  • 4. make vnext-resolve + make vnext-check — no placeholders were outstanding, nothing rewritten
  • 5. make version-sync → plugin.json, marketplace.json, uv.lock
  • 6. make skill-gen — idempotent, no command changes this release
  • 7. whatsnew.ts — deliberately not added: git diff v0.94.0..main -- web/ is empty, so the release ships nothing UI-visible and the popup correctly has nothing new
  • 8/10/11. keboola-expert.md, CLAUDE.md, commands-reference.md — reviewed, no drift (no command added/removed/renamed; these describe device-login behaviour, not panel text)
  • 9. gotchas.md — needed fixing, see below
  • 12. make check exit 0
  • 13. make test-e2e — not run; needs E2E_API_TOKEN / E2E_URL

gotchas.md: #772 changed the panel and left the docs behind

#772 reordered the device-login panel without touching any doc surface. The 0.92.0 gotcha "the one-click link is conditional" quoted the old label ("Or open this link (code pre-filled):") and the old ordering — the pre-filled link used to be last, it is now the headline and the type-it-by-hand URL is the fallback. An agent relaying the panel by keying on that label, or assuming the first URL is the manual one, now picks the wrong line. Rewritten, with the reshuffle tagged v0.95.0.

Added a second entry for press c to copy, because it is absent in exactly the situations an agent operates in — --json, no TTY (a background shell is not one), or no native clipboard command — so an agent must relay the link itself and never tell the user to press c.

After merge

Tag the merge commit — that push is the release:

git fetch origin && git tag v0.95.0 <merge-commit-sha> && git push origin v0.95.0

Re-check the scope against that commit first (checklist step 15): anything merged between now and then needs a changelog bullet, since changelog-check only proves each release has an entry, never that an entry covers every commit under the tag.

🤖 Generated with Claude Code

Covers everything merged since v0.94.0: #768 (uv audit / uv >= 0.12.15),
#772 (device-login "press c to copy") and #773 (test housekeeping).

No `vNEXT` placeholders were outstanding (`make vnext-check` clean), and
no `whatsnew.ts` entry is added -- nothing under `web/` changed this
release, so the popup correctly has nothing new to show.

gotchas.md: #772 reordered the device-login panel without updating the
doc surface. The 0.92.0 "one-click link is conditional" gotcha quoted the
old label ("Or open this link (code pre-filled):") and the old ordering,
so a relay keying on either now picks the wrong line -- rewritten, plus a
new entry for `press c to copy` being absent in exactly the situations an
agent drives (`--json`, no TTY, no clipboard command).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@keboola-pr-reviewer-bot keboola-pr-reviewer-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.

Verdict: needs_human (risk 3/5) · profile keboola-mcp-server

Release PR is mechanically sound but carries scope creep and an admittedly red build, so a human release owner should confirm before tagging.

Impact flags: scope creep · possible rollback re-introduction — see Check Run summary.

Concerns:

  • scratchpad/zajca-round2-replies.md: Unposted PR-review reply drafts committed; unrelated to this release's scope
  • tasks/ship-DMD-1900.md: AI working-note/planning files committed as repo content (6 tasks/* files)
  • pyproject.toml: Release PR to be tagged/published while build is admittedly red pending #773

@keboola-pr-reviewer-bot keboola-pr-reviewer-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.

Verdict: needs_human (risk 2/5) · profile keboola-mcp-server

Release PR 0.95.0 has clean version/changelog mechanics but ships six accidental dev-note files that contradict its declared scope.

Impact flags: scope creep — see Check Run summary.

Concerns:

  • scratchpad/zajca-round2-replies.md: Unposted review-reply drafts committed to repo; internal notes, not release material
  • tasks/ship-DMD-1900.md: Merge-request dev notes committed; outside declared release scope (#772/#768/#773)
  • tasks/pr-703-review.md: PR-703 review write-up committed; contradicts body's 'nothing else' scope claim

Suggested reviewers: keboola/ai-swimlane-kai-assistant

@martinsifra

Copy link
Copy Markdown
Contributor Author

Closing unreleased. The intent was to ship #736 (the merge-request group), which already went out in v0.94.0 — it merged 15 Sep 13:08, the tag followed the same day at 19:56. So there is nothing here that needs releasing today.

What this PR would have released instead is #772 (press c to copy), #768 (uv audit / uv >= 0.12.15) and #773 (the test fix). Those stay on main and will ride whatever the next release is.

One item does need to be carried forward rather than discarded — see the note on the branch below.

🤖 Generated with Claude Code

@martinsifra
martinsifra deleted the release/0.95.0 branch September 17, 2026 08:32
@soustruh soustruh mentioned this pull request Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants