Update databricks-labs-lsql requirement from <0.15,>=0.14.0 to >=0.14.0,<0.17 (#3801)

Updates the requirements on
[databricks-labs-lsql](https://github.com/databrickslabs/lsql) to permit
the latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/databrickslabs/lsql/releases">databricks-labs-lsql's
releases</a>.</em></p>
<blockquote>
<h2>v0.16.0</h2>
<ul>
<li>Let page name adhere to naming restrictions (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/370">#370</a>).
In this release, a new method <code>_clean_resource_name</code> has been
introduced to modify resource names according to the updated naming
convention, allowing only alphanumeric characters, hyphens, and
underscores. The <code>as_lakeview</code> method in the
<code>BaseHandler</code> class now uses this new method to ensure the
<code>Page</code> class name adheres to the new restrictions.
Furthermore, test files for dashboards have been updated to reflect the
change, with a new test function
<code>test_dashboard_metadata_as_lakeview_cleans_page_name</code>
verifying that page names are free of special characters, and an
existing test function modified to handle invalid dashboard YAML files.
These changes improve consistency, reliability, and adherence to best
practices in dashboard naming within the project.</li>
</ul>
<p>Contributors: <a
href="https://github.com/JCZuurmond"><code>@​JCZuurmond</code></a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/databrickslabs/lsql/blob/main/CHANGELOG.md">databricks-labs-lsql's
changelog</a>.</em></p>
<blockquote>
<h2>0.16.0</h2>
<ul>
<li>Let page name adhere to naming restrictions (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/370">#370</a>).
In this release, a new method <code>_clean_resource_name</code> has been
introduced to modify resource names according to the updated naming
convention, allowing only alphanumeric characters, hyphens, and
underscores. The <code>as_lakeview</code> method in the
<code>BaseHandler</code> class now uses this new method to ensure the
<code>Page</code> class name adheres to the new restrictions.
Furthermore, test files for dashboards have been updated to reflect the
change, with a new test function
<code>test_dashboard_metadata_as_lakeview_cleans_page_name</code>
verifying that page names are free of special characters, and an
existing test function modified to handle invalid dashboard YAML files.
These changes improve consistency, reliability, and adherence to best
practices in dashboard naming within the project.</li>
</ul>
<h2>0.15.1</h2>
<ul>
<li>remove duplicate changelog entry (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/366">#366</a>).
In this update, we've improved resource name validation in the
<code>ucx</code> project, first introduced in version 0.14.2. The
validation now restricts resource names to alphanumeric characters,
hyphens, and underscores, addressing usability issues and preventing
problems caused by special characters. A new internal method,
<code>_is_valid_resource_name</code>, checks if a name is valid
according to the defined pattern. The <code>TileMetadata</code> class
has been updated to ensure its <code>id</code> attribute follows the new
validation rules, and <code>Tile</code>, <code>Section</code>, and
<code>Dashboard</code> classes now call the <code>validate</code> method
of the <code>TileMetadata</code> instance if it exists. These changes
promote consistency and correctness in dashboard resources, simplifying
management and interaction for users. As a part of this commit, we also
removed a duplicate changelog entry related to this feature that was
previously present in version 0.15.0.</li>
</ul>
<h2>0.15.0</h2>
<ul>
<li>Validate resource names (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/357">#357</a>).
The recent change in the <code>ucx</code> project enhances resource name
validation to adhere to a new naming convention, restricting names to
alphanumeric characters, hyphens, and underscores. A new method,
<code>_is_valid_resource_name(name: str) -&gt; bool</code>, is
introduced for validating resource names, and the
<code>TileMetadata</code> class has been updated with a
<code>__post_init__</code> method and a <code>validate</code> method for
validation purposes. The <code>Tile</code> and <code>FilterTile</code>
classes also receive a <code>validate</code> method to raise
<code>ValueError</code> for invalid tiles and metadata issues. This
commit introduces new tests for validating tile IDs, tile metadata, and
filter specs while improving error messages for better user
understanding. It also raises <code>ValueError</code> for tiles with
empty content, tiles with names containing spaces, and filter tiles with
invalid widget types, ensuring stricter validation for dashboard
metadata and tile metadata in the <code>ucx</code> project.</li>
</ul>
<h2>0.14.2</h2>
<ul>
<li>Validate resource names (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/357">#357</a>).
This pull request introduces a validation feature to the
<code>ucx</code> project for resource names, specifically for dashboard
tile IDs. The new naming convention restricts resource names to
alphanumeric characters, hyphens, and underscores, enhancing usability
and reducing potential issues caused by special characters. A new
method, <code>_is_valid_resource_name</code>, is implemented to check if
a name is valid based on the defined pattern. The
<code>TileMetadata</code> class is updated to ensure its <code>id</code>
attribute adheres to the new validation rules, and a
<code>validate</code> method is added to raise a <code>ValueError</code>
if the tile metadata is invalid. This method checks if the
<code>id</code> attribute is not empty and if it is a valid resource
name. Additionally, the <code>validate</code> method is updated in the
<code>Tile</code>, <code>Section</code>, and <code>Dashboard</code>
classes to call the <code>validate</code> method of the
<code>TileMetadata</code> instance, if it exists. The pull request also
includes tests for the new validation functionality, ensuring that tile
IDs cannot be empty, must contain only alphanumeric characters, hyphens,
and underscores, and that the <code>validate</code> method detects
duplicate query IDs and widget IDs. This validation helps maintain
consistency and correctness in dashboard resources, making it easier for
users to manage and interact with their dashboards.</li>
<li>Updated runner (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/360">#360</a>).
In this release, we have updated the GitHub Actions workflow for
releasing the project to utilize a protected runner group with the label
<code>linux-ubuntu-latest</code> in the <code>publish</code> job's
<code>runs-on</code> field. This change enhances control and security
over the execution environment, as the protected runner group,
<code>databrickslabs-protected-runner-group</code>, ensures that only
specified runners that meet specific criteria are allowed to execute
jobs. The <code>linux-ubuntu-latest</code> label specifies the desired
runner configuration. Furthermore, the workflow now utilizes an
environment named <code>release</code> and retains the existing
permissions configuration for authenticating to PyPI via OIDC and
signing release artifacts with <code>sigstore-python</code>. This
upgrade to the execution environment preserves essential authentication
and security features, providing improved reliability, maintainability,
and security for the release process while ensuring continued
compatibility and security for publishing activities.</li>
<li>Explicitly install Python 3.12 before running fmt in CI (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/358">#358</a>).
In this release, we have made significant enhancements to our
open-source library aimed at improving reliability, consistency, and
usability for software engineers. A new step installing Python 3.12
explicitly before executing the formatting process in the CI system has
been implemented, ensuring compatibility and consistency with the chosen
Python version. The 'backends.py' file's <code>save_table</code>
function syntax has been updated for better code readability and
maintainability, addressing potential SQL injection issues. The
'model.py' file has undergone refactoring, updating
<code>KeyError</code> exceptions to f-strings for improved consistency
and readability, and the 'polymorphism.py' file has been improved with
new functions and refined error messages for better debugging and
understanding of type assignment issues. Lastly, the 'structs.py' file
in the 'databricks/labs/lsql' package has received updates to ensure
consistent Python version usage, improved error messages, and better SQL
type inference from Python types, enhancing the overall development
experience for adopting engineers.</li>
</ul>
<h2>0.14.1</h2>
<ul>
<li>Changes to work with Databricks SDK <code>v0.38.0</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/350">#350</a>).
In this release, we have upgraded the Databricks SDK to version 0.38.0
from version 0.37.0 to ensure compatibility with the latest SDK and
address several issues. The update includes changes to make the code
compatible with the new SDK version, removing the need for
<code>.as_dict()</code> method calls when creating or updating
dashboards and utilizing a <code>sdk_dashboard</code> variable for
interacting with the Databricks workspace. We also updated the
dependencies to &quot;databricks-labs-blueprint[yaml]&quot; package
version greater than or equal to 0.4.2 and <code>sqlglot</code> package
version greater than or equal to 22.3.1. The <code>test_core.py</code>
file has been updated to address multiple issues (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/349">#349</a>
to <a
href="https://redirect.github.com/databrickslabs/lsql/issues/332">#332</a>)
related to the Databricks SDK and the <code>test_dashboards.py</code>
file has been revised to work with the new SDK version. These changes
improve integration with Databricks' lakeview dashboards, simplify the
code, and ensure compatibility with the latest SDK version, resolving
issues <a
href="https://redirect.github.com/databrickslabs/lsql/issues/349">#349</a>
to <a
href="https://redirect.github.com/databrickslabs/lsql/issues/332">#332</a>.</li>
<li>Specify the minimum required version of <code>databricks-sdk</code>
as 0.37.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/331">#331</a>).
In this release, we have updated the minimum required version of the
<code>databricks-sdk</code> package to 0.37.0 from 0.29.0 in the
<code>pyproject.toml</code> file to ensure compatibility with the latest
version. This change was made necessary due to updates made in issue <a
href="https://redirect.github.com/databrickslabs/lsql/issues/320">#320</a>.
To accommodate any patch release of <code>databricks-sdk</code> with a
major and minor version of 0.37, we have updated the dependency
constraint to use the <code>~=</code> operator, resolving issue <a
href="https://redirect.github.com/databrickslabs/lsql/issues/330">#330</a>.
These changes are intended to enhance the compatibility and stability of
our software.</li>
</ul>
<h2>0.14.0</h2>
<ul>
<li>Added nightly tests run at 4:45am UTC (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/318">#318</a>).
A new nightly workflow has been added to the codebase, designed to
automate a series of jobs every day at 4:45am UTC on the
<code>larger</code> environment. The workflow includes permissions for
writing id-tokens, accessing issues, reading contents and pull-requests.
It checks out the code with a full fetch-depth, installs Python 3.10,
and uses hatch 1.9.4. The key step in this workflow is the execution of
nightly tests using the databrickslabs/sandbox/acceptance action, which
creates issues if necessary. The workflow utilizes several secrets,
including VAULT_URI, GITHUB_TOKEN, ARM_CLIENT_ID, and ARM_TENANT_ID, and
sets the TEST_NIGHTLY environment variable to true. Additionally, the
workflow is part of a concurrency group called
&quot;single-acceptance-job-per-repo&quot;, ensuring that only one
acceptance job runs at a time per repository.</li>
<li>Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/319">#319</a>).
In this version update, the Codecov GitHub Action has been upgraded from
4 to 5, bringing improved functionality and new features. This new
version utilizes the Codecov Wrapper to encapsulate the CLI, enabling
faster updates. Additionally, an opt-out feature has been introduced for
tokens in public repositories, allowing contributors and other members
to upload coverage reports without requiring access to the Codecov
token. The upgrade also includes changes to the arguments:
<code>file</code> is now deprecated and replaced with
<code>files</code>, and <code>plugin</code> is deprecated and replaced
with <code>plugins</code>. New arguments have been added, including
<code>binary</code>, <code>gcov_args</code>,
<code>gcov_executable</code>, <code>gcov_ignore</code>,
<code>gcov_include</code>, <code>report_type</code>,
<code>skip_validation</code>, and <code>swift_project</code>.
Comprehensive documentation on these changes can be found in the release
notes and changelog.</li>
<li>Fixed <code>RuntimeBackend</code> exception handling (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>).
In this release, we have made significant improvements to the exception
handling in the <code>RuntimeBackend</code> component, addressing issues
reported in tickets <a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>,
<a
href="https://redirect.github.com/databrickslabs/lsql/issues/327">#327</a>,
<a
href="https://redirect.github.com/databrickslabs/lsql/issues/326">#326</a>,
and <a
href="https://redirect.github.com/databrickslabs/lsql/issues/325">#325</a>.
We have updated the <code>execute</code> and <code>fetch</code> methods
to handle exceptions more gracefully and changed exception handling from
catching <code>Exception</code> to catching <code>BaseException</code>
for more comprehensive error handling. Additionally, we have updated the
<code>pyproject.toml</code> file to use a newer version of the
<code>databricks-labs-pytester</code> package (0.2.1 to 0.5.0) which may
have contributed to the resolution of these issues. Furthermore, the
<code>test_backends.py</code> file has been updated to improve the
readability and user-friendliness of the test output for the functions
testing if a <code>NotFound</code>, <code>BadRequest</code>, or
<code>Unknown</code> exception is raised when executing and fetching
statements. The <code>test_runtime_backend_use_statements</code>
function has also been updated to print <code>PASSED</code> or
<code>FAILED</code> instead of returning those values. These changes
enhance the robustness of the exception handling mechanism in the
<code>RuntimeBackend</code> class and update related unit tests.</li>
</ul>
<p>Dependency updates:</p>
<ul>
<li>Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/319">#319</a>).</li>
</ul>
<h2>0.13.0</h2>
<ul>
<li>Added <code>escape_name</code> function to escape individual SQL
names and <code>escape_full_name</code> function to escape dot-separated
full names (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/316">#316</a>).
Two new functions, <code>escape_name</code> and
<code>escape_full_name</code>, have been added to the
<code>databricks.labs.lsql.escapes</code> module for escaping SQL names.
The <code>escape_name</code> function takes a single name as an input
and returns it enclosed in backticks, while
<code>escape_full_name</code> handles dot-separated full names by
escaping each individual component. These functions have been ported
from the <code>databrickslabs/ucx</code> repository and are designed to
provide a consistent way to escape names and full names in SQL
statements, improving the robustness of the system by preventing issues
caused by unescaped special characters in SQL names. The test suite
includes various cases, including single names, full names with
different combinations of escaped and unescaped components, and special
characters, with a specific focus on the scenario where the column name
contains a period.</li>
<li>Bump actions/checkout from 4.2.0 to 4.2.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/304">#304</a>).
In this pull request, the <code>actions/checkout</code> dependency is
updated from version 4.2.0 to 4.2.1 in the
<code>.github/workflows/release.yml</code> file. This update includes a
new feature where <code>refs/*</code> are checked out by commit if
provided, falling back to the ref specified by the
<code>@orhantoy</code> user. This change improves the flexibility of the
action, allowing users to specify a commit or branch for checkout. The
pull request also introduces a new contributor, <code>@Jcambass</code>,
who added a workflow file for publishing releases to an immutable action
package. The commits for this release include changes to prepare for the
4.2.1 release, add a workflow file for publishing releases, and check
out other <code>refs/*</code> by commit if provided, falling back to
ref. This pull request has been reviewed and approved by
Dependabot.</li>
<li>Bump actions/checkout from 4.2.1 to 4.2.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/310">#310</a>).
This is a pull request to update the <code>actions/checkout</code>
dependency from version 4.2.1 to 4.2.2, which includes improvements to
the <code>url-helper.ts</code> file that now utilize well-known
environment variables and expanded unit test coverage for the
<code>isGhes</code> function. The <code>actions/checkout</code> action
is commonly used in GitHub Actions workflows for checking out a
repository at a specific commit or branch. The changes in this update
are internal to the <code>actions/checkout</code> action and should not
affect the functionality of the project utilizing this action. The pull
request also includes details on the commits and compatibility score for
the upgrade, and reviewers can manage and merge the request using
Dependabot commands once the changes have been verified.</li>
<li>Bump databrickslabs/sandbox from acceptance/v0.3.0 to 0.3.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/307">#307</a>).
In this release, the <code>databrickslabs/sandbox</code> dependency has
been updated from version <code>acceptance/v0.3.0</code> to
<code>0.3.1</code>. This update includes previously tagged commits, bug
fixes for git-related libraries, and resolution of the <code>unsupported
protocol scheme</code> error. The README has been updated with more
information on using the <code>databricks labs sandbox</code> command,
and installation instructions have been improved. Additionally, there
have been dependency updates for <code>go-git</code> libraries and
<code>golang.org/x/crypto</code> in the <code>/go-libs</code> and
<code>/runtime-packages</code> directories. New commits in this release
allow larger logs from acceptance tests and implement experimental OIDC
refresh functionality. Ignore conditions have been applied to prevent
conflicts with previous versions of the dependency. This update is
recommended for users who want to take advantage of the latest bug fixes
and improvements.</li>
<li>Bump databrickslabs/sandbox from acceptance/v0.3.1 to 0.4.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/315">#315</a>).
In this release, the <code>databrickslabs/sandbox</code> dependency has
been updated from version <code>acceptance/v0.3.1</code> to
<code>0.4.2</code>. This update includes bug fixes, dependency updates,
and additional go-git libraries. Specifically, the <code>Run integration
tests</code> job in the GitHub Actions workflow has been updated to use
the new version of the <code>databrickslabs/sandbox/acceptance</code>
Docker image. The updated version also includes install instructions,
usage instructions in the README, and a modification to provide more
git-related libraries. Additionally, there were several updates to
dependencies, including <code>golang.org/x/crypto</code> version
<code>0.16.0</code> to <code>0.17.0</code>. Dependabot, a tool that
manages dependencies in GitHub projects, is responsible for the update
and provides instructions for resolving any conflicts or merging the
changes into the project. This update is intended to improve the
functionality and reliability of the <code>databrickslabs/sandbox</code>
dependency.</li>
<li>Deprecate <code>Row.as_dict()</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/309">#309</a>).
In this release, we are introducing a deprecation warning for the
<code>as_dict()</code> method in the <code>Row</code> class, which will
be removed in favor of the <code>asDict()</code> method. This change
aims to maintain consistency with Spark's <code>Row</code> behavior and
prevent subtle bugs when switching between different backends. The
deprecation warning will be implemented using Python's warnings
mechanism, including the new annotation in Python 3.13 for static code
analysis. The existing functionality of fetching values from the
database through <code>StatementExecutionExt</code> remains unchanged.
We recommend that clients update their code to use
<code>.asDict()</code> instead of <code>.as_dict()</code> to avoid any
disruptions. A new test case <code>test_row_as_dict_deprecated()</code>
has been added to verify the deprecation warning for
<code>Row.as_dict()</code>.</li>
<li>Minor improvements for
<code>.save_table(mode=&quot;overwrite&quot;)</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/298">#298</a>).
In this release, the <code>.save_table()</code> method has been
improved, particularly when using the <code>overwrite</code> mode. If no
rows are supplied, the table will now be truncated, ensuring consistency
with the mock backend behavior. This change has been optimized for
SQL-based backends, which now perform truncation as part of the insert
for the first batch. Type hints on the abstract method have been updated
to match the concrete implementations. Unit tests and integration tests
have been updated to cover the new functionality, and new methods have
been added to test the truncation behavior in overwrite mode. These
improvements enhance the consistency and efficiency of the
<code>.save_table()</code> method when using <code>overwrite</code> mode
across different backends.</li>
<li>Updated databrickslabs/sandbox requirement to acceptance/v0.3.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/305">#305</a>).
In this release, we have updated the requirement for the
<code>databrickslabs/sandbox</code> package to version
<code>acceptance/v0.3.0</code> in the <code>downstreams.yml</code> file.
This update is necessary to use the latest version of the package, which
includes several bug fixes and dependency updates. The
<code>databrickslabs/sandbox</code> package is used in the acceptance
tests, which are run as part of the CI/CD pipeline. It provides a set of
tools and utilities for developing and testing code in a sandbox
environment. The changelog for this version includes the addition of
install instructions, more git-related libraries, and the modification
of the README to include information about how to use it with the
<code>databricks labs sandbox</code> command. Specifically, the version
of the <code>databrickslabs/sandbox</code> package used in the
<code>acceptance</code> job has been updated from
<code>acceptance/v0.1.4</code> to <code>acceptance/v0.3.0</code>,
allowing the integration tests to be run using the latest version of the
package. The ignore conditions for this PR ensure that Dependabot will
resolve any conflicts that may arise and can be manually triggered with
the <code>@dependabot rebase</code> command.</li>
</ul>
<p>Dependency updates:</p>
<ul>
<li>Bump actions/checkout from 4.2.0 to 4.2.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/304">#304</a>).</li>
<li>Updated databrickslabs/sandbox requirement to acceptance/v0.3.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/305">#305</a>).</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/databrickslabs/lsql/commit/eababdb046f9b524170d0209a5becb116914044e"><code>eababdb</code></a>
Release v0.16.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/371">#371</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/1c9778009dde9368ff6d3bab148a3638d1674344"><code>1c97780</code></a>
Let page name adhere to naming restrictions (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/370">#370</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/f465a166419e6b830e3de9b24ba8734335c4c3ae"><code>f465a16</code></a>
Release v0.15.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/368">#368</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/6e952ccb7ec124ada9864a0959facfd9f4baadd3"><code>6e952cc</code></a>
remove duplicate changelog entry (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/366">#366</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/edc9c197fc71a0c1bd3bfc502540ffab79c13fcb"><code>edc9c19</code></a>
Use greater and less than in sdk version constrain (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/367">#367</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/c2f349ac3dc44f16777004d225347aefb5bba78d"><code>c2f349a</code></a>
Release v0.15.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/365">#365</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/257aedef828a727e9b9ba386ea566a9df5132c03"><code>257aede</code></a>
Release v0.15.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/364">#364</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/a3d7b62c36f87f3b8eb5d182acdb43196386c45f"><code>a3d7b62</code></a>
Remove the no cheat CI check (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/362">#362</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/2410b4a117015f11f67825671fb9dae3fce0389e"><code>2410b4a</code></a>
Log no-lint-disabled CI (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/353">#353</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/19ac5a5c223e865924e68c6407176ada23d7cb12"><code>19ac5a5</code></a>
Release v0.14.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/361">#361</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/databrickslabs/lsql/compare/v0.14.0...v0.16.0">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Cor Zuurmond <[email protected]>

Author: dependabot[bot]

pyproject.toml

@@ -45,7 +45,7 @@ classifiers = [
 ]
 
 dependencies = ["databricks-sdk>=0.40,<0.42",
-                "databricks-labs-lsql>=0.15.0,<0.16.0",
+                "databricks-labs-lsql>=0.16.0,<0.17.0",
                 "databricks-labs-blueprint>=0.10.0,<0.11.0",
                 "PyYAML>=6.0.0,<6.1.0",
                 "sqlglot>=26.7.0,<26.8.0",