version: 1.19.1 (#779)

## version: 1.19.1

## v1.19.1 - 2026-05-14
### Under the Hood
* Silence asyncio DeprecationWarning in LSP connection unit tests by
binding a fresh event loop and using loop.create_future() instead of
bare asyncio.Future().
* Make ToolDefinition.structured_output default to True and require
title in generic_dbt_mcp_tool. Decorator now keyword-only.
* Remove dbt-artifacts-parser from 7 day exclusion
* Fix test_local_mcp_list_metrics_returns_valid_response integration
test

Co-authored-by: DevonFulcher <24593113+DevonFulcher@users.noreply.github.com>

Author: github-actions[bot]

.changes/unreleased/Under the Hood-20260513-085513.yaml

@@ -0,0 +1,6 @@
+## v1.19.1 - 2026-05-14
+### Under the Hood
+* Silence asyncio DeprecationWarning in LSP connection unit tests by binding a fresh event loop and using loop.create_future() instead of bare asyncio.Future().
+* Make ToolDefinition.structured_output default to True and require title in generic_dbt_mcp_tool. Decorator now keyword-only.
+* Remove dbt-artifacts-parser from 7 day exclusion
+* Fix test_local_mcp_list_metrics_returns_valid_response integration test

.changes/unreleased/Under the Hood-20260513-085632.yaml

@@ -7,6 +7,13 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
 
+## v1.19.1 - 2026-05-14
+### Under the Hood
+* Silence asyncio DeprecationWarning in LSP connection unit tests by binding a fresh event loop and using loop.create_future() instead of bare asyncio.Future().
+* Make ToolDefinition.structured_output default to True and require title in generic_dbt_mcp_tool. Decorator now keyword-only.
+* Remove dbt-artifacts-parser from 7 day exclusion
+* Fix test_local_mcp_list_metrics_returns_valid_response integration test
+
 ## v1.19.0 - 2026-05-13
 ### Enhancement or New Feature
 * list_metrics now accepts a list of substrings in the search parameter (results are unioned and deduplicated, fetched in parallel) and prefixes its CSV with a # Note: line whenever description/metadata are trimmed because the response exceeded DBT_MCP_SL_MAX_RESPONSE_CHARS. Trimming is also now scoped to broad listings (result count above metrics_related_max) so a narrow result set always returns full description and metadata.