Skip to content

fix(release): stop plugin builds from taking the latest release, and add a switching guide - #2207

Merged
datlechin merged 2 commits into
mainfrom
fix/release-funnel-leaks
Aug 18, 2026
Merged

fix(release): stop plugin builds from taking the latest release, and add a switching guide#2207
datlechin merged 2 commits into
mainfrom
fix/release-funnel-leaks

Conversation

@datlechin

Copy link
Copy Markdown
Member

Two fixes to the path a new user actually walks, found while auditing where people who reach the project drop off.

releases/latest served a plugin, not the app

gh release create in the plugin workflow never passed --latest=false, so whichever plugin shipped most recently took the latest spot. releases/latest resolved to plugin-oracle-v1.2.20, a two-hash install note, for anyone landing on the releases page or scripting an install. 162 of the repo's releases are plugin builds, so this was the normal state rather than an edge case.

One flag stops it recurring. The current release was re-pointed to v0.65.0 by hand, since the workflow only affects future runs.

build.yml is deliberately untouched: it pins softprops/action-gh-release@v1 by SHA and make_latest only exists from v2, so adding the input there would risk the release job for no gain. With no plugin release claiming latest, app releases hold it on their own.

No page for people switching from another client

The importer reads six other clients and that is documented, but only inside Connection Sharing, which nobody searching for how to move off their current tool would open. docs/switching.mdx is that page, in Getting Started after Installation.

It covers the parts a migration actually trips on:

  • Which client maps to which databases, and where each one keeps its passwords
  • The Keychain versus file split, and choosing Always Allow so a large import does not turn into one prompt per connection
  • What does not come across: saved queries, query history, column widths, shortcuts, with what to do about each
  • The shortcuts worth setting up on day one, and the ones that cannot be rebound
  • Routes for clients the importer does not read: connection URL, project folder

Screenshots reuse the existing image set. Every image path and internal link was checked to exist.

No CHANGELOG entry: documentation-only, plus a CI change with no user-visible app behaviour.

@mintlify

mintlify Bot commented Aug 18, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
TablePro 🟡 Building Aug 18, 2026, 6:40 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@datlechin
datlechin merged commit b4eeff6 into main Aug 18, 2026
7 checks passed
@datlechin
datlechin deleted the fix/release-funnel-leaks branch August 18, 2026 18: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