Skip to content

mcp-data-platform-v0.23.1

Choose a tag to compare

@github-actions github-actions released this 20 Feb 18:50
· 340 commits to main since this release
29e16a7

Bug Fixes

platform_info reports correct build-time version

When server.version was not explicitly set in the YAML config, the platform_info tool reported a hardcoded "1.0.0" instead of the actual build-time version. The Admin UI system info page was unaffected — it already read the correct version from the binary's ldflags.

The hardcoded fallback has been removed from config defaults. The server factory now injects the build-time version (set via -ldflags) when no explicit version is configured. If server.version is set in your YAML, that value continues to take precedence.

Replay inspector preserves SQL newlines

Replaying an audit event containing multi-line SQL from the Tools Inspector corrupted the query by stripping newline characters. Trino received the entire query on a single line, causing parse errors where tokens merged (e.g., )SELECT with no whitespace).

The root cause was React's uncontrolled <textarea defaultValue>, which only applies its value at mount time and ignores subsequent updates during replay. The SQL textarea is now a controlled component that correctly preserves newlines through React's state-driven re-render cycle.

Browser back/forward navigation works in Admin Portal

The browser back and forward buttons previously navigated away from the Admin Portal entirely instead of moving between pages within it. All sidebar navigation was pure React state with no browser history integration.

The Admin Portal now uses path-based routing via history.pushState. URLs are clean paths (/admin/tools, /admin/audit, /admin/knowledge) that are bookmarkable, shareable, and survive page refreshes. The existing Go SPA handler already serves index.html for all unmatched /admin/* paths, so no server-side changes were needed. Tab deep-links continue to work via URL hash fragments (e.g., /admin/tools#help).

Upgrade Notes

No configuration changes required. The server.version config field remains optional — omitting it now correctly reports the binary's build-time version instead of "1.0.0".

Full Changelog: v0.23.0...v0.23.1