[Bug] veadk studio update fails: bundled openviking_sdk-0.1.4 wheel conflicts with openviking-sdk>=0.1.9 #1154

Summary

PR #1151 (31d2c67) raised the requirement in pyproject.toml to openviking-sdk>=0.1.9. Since then, veadk studio update fails while it installs dependencies for the Studio cronjob scheduler.

The update package still ships the pinned openviking_sdk-0.1.4 wheel from STUDIO_DEPENDENCY_WHEELS. uv cannot satisfy both versions, so the update aborts. A fresh veadk studio deploy is not affected.

The 1.1.14 tag points at the same commit, so the 1.1.14 release has the same mismatch.

Environment

• veadk-python: main @ 31d2c67 (tag 1.1.14). Built locally as 1.1.15.dev0+g31d2c67be.
• Provider / region: BytePlus, ap-southeast-1
• Local machine: macOS (arm64), Python 3.12, uv 0.12.3

Steps to reproduce

1. Deploy a Studio from this checkout. This succeeds:

   veadk studio deploy --provider byteplus --region ap-southeast-1 --project default \
     --from-source --user-pool-id <pool-id> --allowed-client-id <client-id> \
     --vefaas-app-name <app-name>

2. Update that Studio from the same checkout:

   veadk studio update --provider byteplus --region ap-southeast-1 --project default \
     --vefaas-app-name <app-name>

Actual result

[Scanner] Dependency installation status: failed
[Scanner] Deployment did not complete | Dependency installation status: failed
Error: Could not finish the Studio update.
Scheduler dependency installation failed: failed. ...
./tokenizers-0.22.2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
./openviking_sdk-0.1.4-py3-none-any.whl
./pydantic-2.12.5-py3-none-any.whl
./vikingdb_python_sdk-0.1.32-py3-none-any.whl
./veadk_python-1.1.15.dev0+g31d2c67be.d20261002-py3-none-any.whl

[faas-build] stderr: Using CPython 3.12.8 interpreter at: /usr/local/bin/python
  × No solution found when resolving dependencies:
  ╰─▶ Because only openviking-sdk<0.1.9 is available
      and veadk-python==1.1.15.dev0+g31d2c67be.d20261002
      depends on openviking-sdk>=0.1.9, we can conclude that
      veadk-python==1.1.15.dev0+g31d2c67be.d20261002 cannot be used.
      And because only veadk-python==1.1.15.dev0+g31d2c67be.d20261002 is
      available and you require veadk-python, we can conclude that your
      requirements are unsatisfiable.

The scheduler is updated before the Studio Application, so the running Studio is left untouched and there is no outage. Still, studio update cannot complete.

Expected result

veadk studio update releases the scheduler, the worker and the Studio function, just as veadk studio deploy does from the same checkout.

Root cause

• studio update builds its package with offline_runtime=False (veadk/cli/cli_frontend.py#L16487-L16492). As a result, build_local_studio_requirements stages the fixed STUDIO_DEPENDENCY_WHEELS list next to the local veadk wheel (veadk/cli/studio_package.py#L249-L250).
• That list still pins openviking_sdk-0.1.4 (veadk/cli/studio_dependencies.py#L96-L102). Since fix: adapt openviking backend to options api #1151, however, the package requires openviking-sdk>=0.1.9 (pyproject.toml#L58).
• veadk studio deploy --from-source keeps the default offline_runtime=True (veadk/cli/cli_frontend.py#L15952). That path resolves from uv.lock, which locks openviking-sdk 0.1.9, so first deploys still work.
• STUDIO_DEPENDENCY_WHEELS is shared by both providers. Volcengine studio update is therefore probably affected as well. I have not verified this on Volcengine.

Suggested fix

Bump the pinned wheel to the version locked in uv.lock, in veadk/cli/studio_dependencies.py:

StudioDependencyWheel(
    filename="openviking_sdk-0.1.9-py3-none-any.whl",
    url=(
        "https://files.pythonhosted.org/packages/47/d6/"
        "aa82551f9c5d06ce682b9194c784beeb16478ce103d650ed8e8b487b1aa7/"
        "openviking_sdk-0.1.9-py3-none-any.whl"
    ),
    sha256="6057f3ab921cee4697a7b424948347669cb7b8e04439f305503d8ab7132af3ce",
),

Also update the expected filename in tests/cli/test_studio_deploy_target.py#L73.

I applied this change locally, and the result was:

• veadk studio update completed on BytePlus. The scheduler, the worker and the Studio function were all released.
• The Studio packaging, update and release tests passed (333 passed).

To keep this from coming back, a test could check each wheel in STUDIO_DEPENDENCY_WHEELS and BYTEPLUS_STUDIO_DEPENDENCY_WHEELS against the version locked in uv.lock. A dependency bump in pyproject.toml would then fail in CI instead of silently breaking studio update.