steve/databricks-cli
steve
/
databricks-cli
mirror of https://github.com/databricks/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
databricks-cli/NEXT_CHANGELOG.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

13 lines
240 B
Markdown
Raw Permalink Normal View History

Enable Automated tagging workflow (#2361) ## Changes Enable Automated tagging workflow. The workflow uses the `tagging.py` script to: * Flush the NEXT_CHANGELOG.md` file into the `CHANGELOG.md`. * Create a Release commit and push it to `main` (without a PR) * Create a tag for the release. Usage and Changelog management details can be found in [go/deco/release](go/deco/release). This PR does: * Added `cli_legacy` mode. Each SDK has it's own "mode" used to determine which templates are to be used. * `api_changelog: true` enables API changelog to be appended to NEXT_CHANGELOG when generating the SDK. * Removed `.codegen/changelog.md.tmpl`. Changelog templates are now part of universe. * Workflow and `tagging.py` files are synced from universe as part of SDK generation. This allows us to test them and keep them in sync with other SDKs. ## Tests Workflow enabled in databricks/terraform-provider-databricks --------- Co-authored-by: Andrew Nester <andrew.nester@databricks.com>
2025-03-06 15:30:01 +00:00
# NEXT CHANGELOG
## Release v0.243.1
### CLI
Fixed "can't evaluate field Name in type interface{}" for `databricks queries list` (#2451) ## Changes Fixes #1888 ## Why `databricks queries list` is using override to define a template to display a list in a nice table form. This Go template was referencing to non existing anymore fields and hence failing. ## Tests Added acceptance test
2025-03-10 08:05:15 +00:00
* Fixed "can't evaluate field Name in type interface{}" for "databricks queries list" command ([#2451](https://github.com/databricks/cli/pull/2451))
Enable Automated tagging workflow (#2361) ## Changes Enable Automated tagging workflow. The workflow uses the `tagging.py` script to: * Flush the NEXT_CHANGELOG.md` file into the `CHANGELOG.md`. * Create a Release commit and push it to `main` (without a PR) * Create a tag for the release. Usage and Changelog management details can be found in [go/deco/release](go/deco/release). This PR does: * Added `cli_legacy` mode. Each SDK has it's own "mode" used to determine which templates are to be used. * `api_changelog: true` enables API changelog to be appended to NEXT_CHANGELOG when generating the SDK. * Removed `.codegen/changelog.md.tmpl`. Changelog templates are now part of universe. * Workflow and `tagging.py` files are synced from universe as part of SDK generation. This allows us to test them and keep them in sync with other SDKs. ## Tests Workflow enabled in databricks/terraform-provider-databricks --------- Co-authored-by: Andrew Nester <andrew.nester@databricks.com>
2025-03-06 15:30:01 +00:00
### Bundles
### Internal
### API Changes