Release v0.7.2 (#231)

* Fixed dashboard deployment/creation
([#230](#230)). The recent
changes to our open-source library address issues related to dashboard
deployment and creation, enhancing their reliability and consistency.
The `deploy_dashboard` function has been deprecated in favor of the more
accurate `create_dashboard` function, which now includes a `publish`
flag. A `validate` method has been added to the `Tile`, `MarkdownTile`,
and `QueryTile` classes to raise an error if the dashboard is invalid.
The `test_dashboards.py` file has been updated to reflect these changes.
These enhancements address issues
[#222](#222),
[#229](#229), and partially
resolve [#220](#220). The
commit includes an image of a dashboard created through the deprecated
`deploy_dashboard` method. These improvements ensure better dashboard
creation, validation, and deployment, while also maintaining backward
compatibility through the deprecation of `deploy_dashboard`.

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Version changelog
 
+## 0.7.2
+
+* Fixed dashboard deployment/creation ([#230](https://github.com/databrickslabs/lsql/issues/230)). The recent changes to our open-source library address issues related to dashboard deployment and creation, enhancing their reliability and consistency. The `deploy_dashboard` function has been deprecated in favor of the more accurate `create_dashboard` function, which now includes a `publish` flag. A `validate` method has been added to the `Tile`, `MarkdownTile`, and `QueryTile` classes to raise an error if the dashboard is invalid. The `test_dashboards.py` file has been updated to reflect these changes. These enhancements address issues [#222](https://github.com/databrickslabs/lsql/issues/222), [#229](https://github.com/databrickslabs/lsql/issues/229), and partially resolve [#220](https://github.com/databrickslabs/lsql/issues/220). The commit includes an image of a dashboard created through the deprecated `deploy_dashboard` method. These improvements ensure better dashboard creation, validation, and deployment, while also maintaining backward compatibility through the deprecation of `deploy_dashboard`.
+
+
 ## 0.7.1
 
 * Bump sigstore/gh-action-sigstore-python from 2.1.1 to 3.0.0 ([#224](https://github.com/databrickslabs/lsql/issues/224)). In version 3.0.0 of sigstore/gh-action-sigstore-python, several changes, additions, and removals have been implemented. Notably, certain settings such as fulcio-url, rekor-url, ctfe, and rekor-root-pubkey have been removed. Additionally, the output settings signature, certificate, and bundle have also been removed. The inputs are now parsed according to POSIX shell lexing rules for better consistency. The release-signing-artifacts setting no longer causes a hard error when used under the incorrect event. Furthermore, various deprecations present in sigstore-python's 2.x series have been resolved. The default suffix has been changed from .sigstore to .sigstore.json, in line with Sigstore's client specification. The release-signing-artifacts setting now defaults to true. This version also includes several bug fixes and improvements to support CI runners that use PEP 668 to constrain global package prefixes.

src/databricks/labs/lsql/__about__.py

@@ -1 +1 @@
-__version__ = "0.7.1"
+__version__ = "0.7.2"