databricks-tellr 0.3.11.dev9__tar.gz → 0.3.11.dev10__tar.gz

{databricks_tellr-0.3.11.dev9 → databricks_tellr-0.3.11.dev10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: databricks-tellr
-Version: 0.3.11.dev9
+Version: 0.3.11.dev10
 Summary: Tellr deployment tooling for Databricks Apps
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown

{databricks_tellr-0.3.11.dev9 → databricks_tellr-0.3.11.dev10}/databricks_tellr/deploy.py

@@ -1233,7 +1233,6 @@ def _write_requirements(
                           (e.g., "./wheels/databricks_tellr_app-0.1.18-py3-none-any.whl")
                           instead of installing from PyPI
     """
-    extra_pins: list[str] = []
     if local_wheel_path:
         # Use local wheel reference - pip will install from uploaded wheel
         package_line = local_wheel_path
@@ -1250,56 +1249,16 @@ def _write_requirements(
             package_line = f"databricks-tellr-app=={resolved_version}"
         else:
             package_line = "databricks-tellr-app"
-        extra_pins = _RESOLVER_SPEEDUP_PINS
 
     content = "\n".join(
         [
             "# Generated by databricks-tellr",
             package_line,
-            *extra_pins,
         ]
     )
     (staging_dir / "requirements.txt").write_text(content)
 
 
-# The Databricks Apps BUILD phase kills deployments whose install exceeds the
-# ~10-minute startup budget, and on FEVM workspaces its connectivity to the
-# PyPI mirror is known-flaky (see #fevm-feedback / #apa-apps, July 2026), so
-# every avoidable metadata fetch is a timeout risk. The app's ranged direct
-# dependencies plus unpinned transitives (databricks-sdk, mlflow[databricks],
-# the langchain/unitycatalog cluster) send pip's resolver into heavy
-# backtracking as new versions land on PyPI — observed taking >6.5 min to
-# resolve even locally on a healthy connection, which failed every Apps
-# deploy (including previously-good stable versions) with "App process did
-# not start within 10 minutes".
-#
-# These pins are one known-good resolution (pip install --dry-run --report of
-# the app wheel, July 2026) and short-circuit the search. They must always
-# satisfy the ranges declared in packages/databricks-tellr-app/pyproject.toml;
-# refresh them with a new dry-run resolve if that file's constraints change.
-_RESOLVER_SPEEDUP_PINS = [
-    "# Resolver-speedup pins (see _RESOLVER_SPEEDUP_PINS in databricks_tellr.deploy)",
-    "databricks-agents==1.11.0",
-    "databricks-ai-bridge==0.21.0",
-    "databricks-ai-search==0.76",
-    "databricks-connect==16.1.7",
-    "databricks-sdk==0.120.0",
-    "databricks-vectorsearch==0.75",
-    "langchain==1.0.5",
-    "langchain-classic==1.0.0",
-    "langchain-community==0.4.1",
-    "langchain-core==1.0.4",
-    "langgraph==1.0.10",
-    "langgraph-prebuilt==1.0.10",
-    "langsmith==0.9.5",
-    "litellm==1.80.11",
-    "mlflow==3.14.0",
-    "mlflow-skinny==3.14.0",
-    "unitycatalog-ai==0.3.2",
-    "unitycatalog-langchain==0.3.0",
-]
-
-
 def _resolve_installed_app_version() -> str | None:
     """Try to resolve the installed version of databricks-tellr-app."""
     try:

{databricks_tellr-0.3.11.dev9 → databricks_tellr-0.3.11.dev10}/databricks_tellr.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: databricks-tellr
-Version: 0.3.11.dev9
+Version: 0.3.11.dev10
 Summary: Tellr deployment tooling for Databricks Apps
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown

{databricks_tellr-0.3.11.dev9 → databricks_tellr-0.3.11.dev10}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "databricks-tellr"
-version = "0.3.11.dev9"
+version = "0.3.11.dev10"
 description = "Tellr deployment tooling for Databricks Apps"
 readme = "README.md"
 requires-python = ">=3.10"