diff --git a/.nextchanges/bundles/ai-runtime-code-source-dir.md b/.nextchanges/bundles/ai-runtime-code-source-dir.md
index 4590fb6be8..10249ea342 100644
--- a/.nextchanges/bundles/ai-runtime-code-source-dir.md
+++ b/.nextchanges/bundles/ai-runtime-code-source-dir.md
@@ -1 +1 @@
-For jobs where `ai_runtime_task.code_source_path` is a relative path to a local directory, the directory is now packaged into a tarball (honoring `.gitignore` and `sync.include`/`sync.exclude`), uploaded during deployment, and `code_source_path` is rewritten to the uploaded workspace path.
+For jobs where `ai_runtime_task.code_source_path` is a relative path to a local directory, the directory is now packaged into a tarball (honoring `.gitignore` and `sync.include`/`sync.exclude`), uploaded during deployment, and `code_source_path` is rewritten to the uploaded workspace path. ([#6110](https://github.com/databricks/cli/pull/6110))
diff --git a/.nextchanges/bundles/bundle-init-json-output.md b/.nextchanges/bundles/bundle-init-json-output.md
index 4d9e776336..e8d4f0bbe6 100644
--- a/.nextchanges/bundles/bundle-init-json-output.md
+++ b/.nextchanges/bundles/bundle-init-json-output.md
@@ -1 +1 @@
-Added JSON output to `bundle init`. Running `databricks bundle init <template> -o json` now reports the files the template wrote, relative to the output directory. This lets callers that pass `--output-dir` learn where the template materialized instead of assuming the output is a single directory named after the project. The default text output is unchanged.
+Added JSON output to `bundle init`. Running `databricks bundle init <template> -o json` now reports the files the template wrote, relative to the output directory. This lets callers that pass `--output-dir` learn where the template materialized instead of assuming the output is a single directory named after the project. The default text output is unchanged. ([#6161](https://github.com/databricks/cli/pull/6161))
diff --git a/.nextchanges/bundles/deprecate-terraform-engine.md b/.nextchanges/bundles/deprecate-terraform-engine.md
index 955c523bed..89955b50e3 100644
--- a/.nextchanges/bundles/deprecate-terraform-engine.md
+++ b/.nextchanges/bundles/deprecate-terraform-engine.md
@@ -1 +1 @@
-The terraform deployment engine is deprecated and will stop working in a future version of the CLI. Setting `bundle.engine: terraform` now emits a deprecation warning. See https://docs.databricks.com/aws/en/dev-tools/bundles/direct for how to migrate to the direct deployment engine.
+The terraform deployment engine is deprecated and will stop working in a future version of the CLI. Setting `bundle.engine: terraform` now emits a deprecation warning. See https://docs.databricks.com/aws/en/dev-tools/bundles/direct for how to migrate to the direct deployment engine. ([#6099](https://github.com/databricks/cli/pull/6099))
diff --git a/.nextchanges/bundles/empty-grants-migrate.md b/.nextchanges/bundles/empty-grants-migrate.md
index fa6707d368..3bc20796f4 100644
--- a/.nextchanges/bundles/empty-grants-migrate.md
+++ b/.nextchanges/bundles/empty-grants-migrate.md
@@ -1 +1 @@
-Fixed the direct deployment engine planning a spurious `create` for an empty `grants: []` list. Terraform records no grants resource for such a list, so `bundle plan` after `bundle deployment migrate` no longer reports an action for it. Emptying a previously deployed list still revokes the grants, after which the node is dropped from the deployment state instead of being reported as unchanged forever.
+Fixed the direct deployment engine planning a spurious `create` for an empty `grants: []` list. Terraform records no grants resource for such a list, so `bundle plan` after `bundle deployment migrate` no longer reports an action for it. Emptying a previously deployed list still revokes the grants, after which the node is dropped from the deployment state instead of being reported as unchanged forever. ([#6039](https://github.com/databricks/cli/pull/6039))
diff --git a/.nextchanges/bundles/pipeline-allow-duplicate-names-converges.md b/.nextchanges/bundles/pipeline-allow-duplicate-names-converges.md
index 147ee5fbc6..4629884575 100644
--- a/.nextchanges/bundles/pipeline-allow-duplicate-names-converges.md
+++ b/.nextchanges/bundles/pipeline-allow-duplicate-names-converges.md
@@ -1 +1 @@
-Fixed a pipeline with `allow_duplicate_names: true` never converging on the direct engine: the field is only accepted on create/update and is never returned by the pipelines GET API, so every subsequent `bundle plan` reported the pipeline as a perpetual update.
+Fixed a pipeline with `allow_duplicate_names: true` never converging on the direct engine: the field is only accepted on create/update and is never returned by the pipelines GET API, so every subsequent `bundle plan` reported the pipeline as a perpetual update. ([#6076](https://github.com/databricks/cli/pull/6076))
diff --git a/.nextchanges/bundles/remote-already-set-input-only.md b/.nextchanges/bundles/remote-already-set-input-only.md
index 6782e5a350..9e283d6b8a 100644
--- a/.nextchanges/bundles/remote-already-set-input-only.md
+++ b/.nextchanges/bundles/remote-already-set-input-only.md
@@ -1 +1 @@
-direct: A local change to an input-only field (one the API accepts on write but never returns on read, e.g. pipelines' `run_as` or external locations' `skip_validation`) is no longer silently skipped when the new value coincidentally matches the field's fabricated remote value. Previously such a change could hit the `remote_already_set` shortcut and be dropped from the plan.
+direct: A local change to an input-only field (one the API accepts on write but never returns on read, e.g. pipelines' `run_as` or external locations' `skip_validation`) is no longer silently skipped when the new value coincidentally matches the field's fabricated remote value. Previously such a change could hit the `remote_already_set` shortcut and be dropped from the plan. ([#6112](https://github.com/databricks/cli/pull/6112))
diff --git a/.nextchanges/bundles/revert-redact-sensitive.md b/.nextchanges/bundles/revert-redact-sensitive.md
index da522598e7..d71f936154 100644
--- a/.nextchanges/bundles/revert-redact-sensitive.md
+++ b/.nextchanges/bundles/revert-redact-sensitive.md
@@ -1 +1 @@
-Revert usage of RedactiveSenstiveFields (added in [#5896](https://github.com/databricks/cli/pull/5896), released in 1.10.0) which lead to incorrect behaviour (permanent drift) for duration field in Postgres resources.
+Revert usage of RedactiveSenstiveFields (added in [#5896](https://github.com/databricks/cli/pull/5896), released in 1.10.0) which lead to incorrect behaviour (permanent drift) for duration field in Postgres resources ([#6179](https://github.com/databricks/cli/pull/6179)).
diff --git a/.nextchanges/bundles/schema-field-documentation.md b/.nextchanges/bundles/schema-field-documentation.md
new file mode 100644
index 0000000000..6d3d62d7bb
--- /dev/null
+++ b/.nextchanges/bundles/schema-field-documentation.md
@@ -0,0 +1 @@
+Document postgres resource fields in the json schema ([#6164](https://github.com/databricks/cli/pull/6164), [#6163](https://github.com/databricks/cli/pull/6163)).
diff --git a/.nextchanges/bundles/vector-search-index-pending-deletion.md b/.nextchanges/bundles/vector-search-index-pending-deletion.md
index 31dd3579d1..a5546bb7d4 100644
--- a/.nextchanges/bundles/vector-search-index-pending-deletion.md
+++ b/.nextchanges/bundles/vector-search-index-pending-deletion.md
@@ -1 +1 @@
-direct: Recreating a `vector_search_indexes` resource no longer fails with "Index ... is currently pending deletion" when the backend has not yet released the index name. The create is now retried until the name becomes available.
+direct: Recreating a `vector_search_indexes` resource no longer fails with "Index ... is currently pending deletion" when the backend has not yet released the index name. The create is now retried until the name becomes available. ([#6143](https://github.com/databricks/cli/pull/6143))
diff --git a/.nextchanges/cli/skills-fs-routing.md b/.nextchanges/cli/skills-fs-routing.md
index 183b98f91d..7b167dfcbe 100644
--- a/.nextchanges/cli/skills-fs-routing.md
+++ b/.nextchanges/cli/skills-fs-routing.md
@@ -1 +1 @@
-Support `dbfs:/Skills/...` paths in `databricks fs` commands, routed to the Files API.
+Support `dbfs:/Skills/...` paths in `databricks fs` commands, routed to the Files API. ([#6147](https://github.com/databricks/cli/pull/6147))
diff --git a/.nextchanges/dependency-updates/databricks-sdk-go-v0.166.0.md b/.nextchanges/dependency-updates/databricks-sdk-go-v0.166.0.md
index b833726dbb..522d6643c1 100644
--- a/.nextchanges/dependency-updates/databricks-sdk-go-v0.166.0.md
+++ b/.nextchanges/dependency-updates/databricks-sdk-go-v0.166.0.md
@@ -1 +1 @@
-Bump `github.com/databricks/databricks-sdk-go` from v0.165.0 to v0.166.0.
+Bump `github.com/databricks/databricks-sdk-go` from v0.165.0 to v0.166.0. ([#6175](https://github.com/databricks/cli/pull/6175))
diff --git a/.nextchanges/dependency-updates/tf-provider-1.124.0.md b/.nextchanges/dependency-updates/tf-provider-1.124.0.md
index a5a0322648..8a054c9330 100644
--- a/.nextchanges/dependency-updates/tf-provider-1.124.0.md
+++ b/.nextchanges/dependency-updates/tf-provider-1.124.0.md
@@ -1 +1 @@
-Upgrade Terraform provider to 1.124.0
+Upgrade Terraform provider to 1.124.0. ([#6174](https://github.com/databricks/cli/pull/6174))