- Add ChangelogList component and changelog data fetcher
- Add platform icons for install tabs
- Add sync-changelog workflow (triggers on release publish)
- Add changelog sync script and releases-cn.json data
- Update InstallTabs and docs meta
- Extract LandingNav into shared component with lang/active props
- Add Home and Community nav items with active state highlighting
- Deepen landing background (#0b1120), strengthen hero glow, add CSS noise texture
- Sync changelog page to use shared nav and semantic colors
- Create /[lang]/community page with QQ, WeChat, Discord, GitHub Discussions
- Migrate landing CSS from raw classes to Tailwind v4 utilities (~1180 → ~680 lines)
- Add @theme block with landing design tokens
- Shrink download button, add OS auto-detection
- Nav bar transparent at top, glass effect on scroll
- Adjust hero spacing, title size, background color
- Remove white background from logo and favicon
- Force subtitle to single line on desktop
Allow saving connections without a name by generating one in the format
`{DbType}_{random4chars}` (e.g. Neo4j_a3f2). Update placeholder text
to inform users about auto-generation.
Add full support for Highgo database, a PostgreSQL-compatible Chinese
domestic database. Includes database type definition, connection dialog,
agent driver mapping, and database icon.
Add list_objects support for agent-driven databases (Dameng, Oracle, etc.)
and ExternalDriver plugin connections. SQL Server dbo schema now uses
listObjects to display grouped object nodes including routines.
- Add list_objects RPC to JDBC agent plugin
- Add extract_agent and ExternalDriver branches in list_objects_core
- Add get_object_source support for agent connections
- Click function/procedure nodes to view source via object browser
- Fix duplicate tree node IDs when same name exists as view and function
On Windows, when both `bin/dbx-jdbc-plugin` (Unix shell script) and
`bin/dbx-jdbc-plugin.bat` exist, always prefer the .bat file instead of
only falling back when the original path doesn't exist.
GITHUB_TOKEN events don't trigger other workflows, so the release
promotion in promote-release never fired qq-notify.yml. Move the
notification inline as a dependent job.
t8y2