Skip to content

deps(actions): bump actions/setup-python from 5.1.1 to 5.6.0 - #7

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-5.6.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-5.6.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 19, 2026 •

Copy link
Copy Markdown

Bumps actions/setup-python from 5.1.1 to 5.6.0.

Release notes

Sourced from actions/setup-python's releases.

v5.6.0

What's Changed

Full Changelog: actions/setup-python@v5...v5.6.0

v5.5.0

What's Changed

Enhancements:

Bug fixes:

Dependency updates:

New Contributors

Full Changelog: actions/setup-python@v5...v5.5.0

v5.4.0

What's Changed

Enhancements:

Documentation changes:

Dependency updates:

New Contributors

... (truncated)

Commits
  • a26af69 Bump ts-jest from 29.1.2 to 29.3.2 (#1081)
  • 30eafe9 Bump prettier from 2.8.8 to 3.5.3 (#1046)
  • 5d95bc1 Bump semver and @​types/semver (#1091)
  • 6ed2c67 Fix for Candidate Not Iterable Error (#1082)
  • e348410 Remove Ubuntu 20.04 from workflows due to deprecation from 2025-04-15 (#1065)
  • 8d9ed9a Add e2e Testing for free threaded and Bump @​action/cache from 4.0.0 to 4.0.3 ...
  • 19e4675 Add support for .tool-versions file in setup-python (#1043)
  • 6fd11e1 Bump @​actions/glob from 0.4.0 to 0.5.0 (#1015)
  • 9e62be8 Support free threaded Python versions like '3.13t' (#973)
  • 6ca8e85 Bump @​vercel/ncc from 0.38.1 to 0.38.3 (#1016)
  • Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot @github

dependabot Bot commented on behalf of github May 19, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.1.1 to 5.6.0.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v5.1.1...a26af69)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: 5.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/setup-python-5.6.0 branch from 3d06a62 to 531ce91 Compare May 27, 2026 12:27
ozzaii added a commit that referenced this pull request May 27, 2026
… fix for the rc1 ship blocker

After three days of partial fixes (spec blocklist `"cli"` removal `3d2900ce`, eager-import attempt `8dd2f098` (reverted), runtime hook `99c951a7`), this commit is the actual root-cause fix.

ROOT CAUSE: livekit-agents 1.x's ``livekit/agents/__init__.py:23`` does a single

    from . import cli, inference, ipc, llm, metrics, stt, tokenize, tts, utils, vad, voice

statement. PyInstaller's frozen importer does NOT bind submodules onto the parent package in the comma-list order the way CPython's normal importer does. When the chained load reaches ``voice.agent_session.py:26`` (``from .. import cli, ...``) — voice is the LAST item in the list — ``cli`` has been imported but is NOT yet bound on the parent, so ``cli`` lookup fails: ``ImportError: cannot import name 'cli' from partially initialized module 'livekit.agents'``.

FIX: split the single statement into two with ``cli`` first. Python evaluates each statement independently, so the parent has ``cli`` bound before the rest of the chain runs.

Implementation:
- ``scripts/dist/patch_livekit_agents_init.py`` — idempotent patch script. Locates the .venv (and import-resolved fallback) ``livekit/agents/__init__.py``, rewrites the offending line, and PURGES the stale ``__pycache__/__init__.cpython-*.pyc`` (otherwise PyInstaller silently bundles the cached unpatched bytecode — the actual repro we hit on the 6th rebuild attempt today).
- ``scripts/build_sidecar.py`` — calls the patch script as ``_apply_livekit_agents_init_patch()`` from inside ``run_pyinstaller()`` before invoking ``pyinstaller``. The build pipeline now self-applies the patch on every freeze.

Spawn-context test matrix (build #7, patch + pycache purge):
| Spawn                                        | Result |
|----------------------------------------------|--------|
| ``./vibemix-core --help`` (TTY)              | ✅     |
| ``./vibemix-core --wizard``                  | ✅     |
| ``./vibemix-core --session``                 | ✅     |
| ``./vibemix-core </dev/null`` (closed stdin) | ✅     |
| ``subprocess.Popen(stdin=PIPE)``             | ✅     |
| ``subprocess.Popen(env=Tauri-vars, cwd=..)`` | ✅     |
| Tauri's ``app.shell().command()`` spawn      | ❌     |

Last row is a SEPARATE bug in ``tauri-plugin-shell`` 2.3's spawn implementation (it's the only spawn that still crashes despite the bundle being healthy under every other invocation — same env, same stdio, same cwd). Likely fix is replacing the ``app.shell().command(...)`` call in ``tauri/src-tauri/src/sidecar.rs:174,198`` with ``std::process::Command::new(...)`` + manual stdio capture, or upgrading tauri-plugin-shell. **Production ship recommendation:** the signed CI .app launched via ``launchd`` is a different spawn flavour again — it MIGHT bypass the tauri-plugin-shell-specific bug, but MUST be smoke-tested before declaring rc1 production-clean.

Workaround for ear-pass NOW: ``VIBEMIX_DEV_SIDECAR=1 cargo run --no-default-features`` from ``tauri/src-tauri/`` uses the dev-source path (``uv run python -m vibemix``), bypassing the bundle entirely. Confirmed live: ``:8765`` bound, sidecar attached, full session loop active.

Regression test (``tests/dist/test_livekit_agents_init_patch.py``): three assertions — patch script exists, ``--dry-run`` succeeds idempotently, and ``build_sidecar.py::run_pyinstaller`` invokes ``_apply_livekit_agents_init_patch()``. Stack alongside the spec-blocklist (``test_spec_blocklist_keeps_livekit_cli.py``) and runtime-hook (``test_runtime_hooks_livekit_agents.py``) regression tests for a 9-test bundle-boot safety net.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants