chore(deps): update github actions#5488
Conversation
STT Test Resultsβ Could not parse test results: [Errno 2] No such file or directory: 'test-results.xml' Triggered by workflow run #2835 |
|
/test-stt |
f6c98f5 to
67b4d33
Compare
7f8f90b to
1d5b7c8
Compare
19f9247 to
f7b4342
Compare
f7b4342 to
a2aeb1f
Compare
e8933dd to
a3d01c5
Compare
4c3c018 to
fc2110b
Compare
fc2110b to
44d8b9c
Compare
| uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6 | ||
| with: | ||
| python-version: "3.11" | ||
| python-version: "3.14" |
There was a problem hiding this comment.
π© cibuildwheel build filter missing for blockguard and blingfire
The livekit-durable cibuildwheel config explicitly lists build = "cp310-* cp311-* cp312-* cp313-* cp314-*", but livekit-blockguard and livekit-blingfire have no build key. This means they rely on cibuildwheel's default build matrix. This is pre-existing and not introduced by this PR, but now that the host Python is 3.14, it's worth verifying that the default cibuildwheel matrix includes cp314 wheels if that's desired for these packages.
Was this helpful? React with π or π to provide feedback.
2edae27 to
c7c6d60
Compare
c7c6d60 to
f584e20
Compare
| - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6 | ||
| with: | ||
| python-version: "3.12" | ||
| python-version: "3.14" |
There was a problem hiding this comment.
π© Unit and integration tests no longer run on any Python version below 3.14
Prior to this PR, unit-tests, blockguard-tests, evaluation, evals, test-realtime, test-stt, and download-stats all ran on Python 3.12 (or 3.10/3.11 for some build jobs). After this PR, they all run exclusively on 3.14. The only CI job that still exercises an older Python is the type-check matrix in ci.yml, which covers 3.10 and 3.13. This means runtime regressions specific to Python 3.10β3.13 (e.g. behavioral differences in asyncio, typing, stdlib changes) would no longer be caught by tests β only type-checking. This is a deliberate tradeoff but worth noting since AGENTS.md:125 states "Python 3.10+ compatibility required".
Was this helpful? React with π or π to provide feedback.
f584e20 to
ca3d212
Compare
ca3d212 to
3a814b9
Compare
021ea0d to
00ddbc1
Compare
dcc9bb5 to
3b6d687
Compare
Generated by renovateBot
3b6d687 to
165bb2a
Compare
This PR contains the following updates:
v5.0.5βv5.1.09c091bbβ3d3c42ea309ff8βece7cb0v8.0.0βv8.3.0v8.3.2(+1)cef2210βba38be93.12β3.143.10β3.143.11β3.14Release Notes
actions/cache (actions/cache)
v5.1.0Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.1.0
astral-sh/setup-uv (astral-sh/setup-uv)
v8.3.0Compare Source
v8.2.0: π New inputsquietanddownload-from-astral-mirrorCompare Source
Changes
This release brings two new inputs and a few bug fixes.
New inputs
Lets talk about the new inputs first.
quiet
Pretty simple. It turns of all
infologgings. Useful if you use this in a composite action and are not interested in all the details.In the upcoming releases we will add log groups to fully implement support for "less noise"
download-from-astral-mirror
In some cases you may want to directly use the fallback of checking for available versions and downloading releases from GitHub instead of using the astral.sh mirror. Setting
download-from-astral-mirror: falseallows you to do that.Bugfixes
When using the astral.sh mirror to query available versions and download releases (done by default) we now stop sending the GitHub token in the header. The mirror never looked at it but we shouldn't be handing out that data even if it is just a short lived token.
All other bugfixes try to limit the impact of failed GitHub queries due to retries and other faults.
We couldn't pinpoint all rootcauses yet but added more logging for error cases to track them down.
π Bug fixes
π Enhancements
download-from-astral-mirrorinput @βeifinger (#β897)π§° Maintenance
β¬οΈ Dependency updates
v8.1.0: π New inputno-projectCompare Source
Changes
This add the a new boolean input
no-project.It only makes sense to use in combination with
activate-environment: trueand will append--no projectto theuv venvcall. This is for example useful if you have a pyproject.toml file with parts unparseable by uvπ Enhancements
π§° Maintenance
π Documentation
β¬οΈ Dependency updates
actions/python-versions (python)
v3.14.6: 3.14.6Compare Source
Python 3.14.6
v3.14.5: 3.14.5Compare Source
Python 3.14.5
v3.14.4: 3.14.4Compare Source
Python 3.14.4
v3.14.3: 3.14.3Compare Source
Python 3.14.3
v3.14.2: 3.14.2Compare Source
Python 3.14.2
v3.14.1: 3.14.1Compare Source
Python 3.14.1
v3.14.0: 3.14.0Compare Source
Python 3.14.0
v3.13.14: 3.13.14Compare Source
Python 3.13.14
v3.13.13: 3.13.13Compare Source
Python 3.13.13
v3.13.12: 3.13.12Compare Source
Python 3.13.12
v3.13.11: 3.13.11Compare Source
Python 3.13.11
v3.13.10: 3.13.10Compare Source
Python 3.13.10
v3.13.9: 3.13.9Compare Source
Python 3.13.9
v3.13.8: 3.13.8Compare Source
Python 3.13.8
v3.13.7: 3.13.7Compare Source
Python 3.13.7
v3.13.6: 3.13.6Compare Source
Python 3.13.6
v3.13.5: 3.13.5Compare Source
Python 3.13.5
v3.13.4: 3.13.4Compare Source
Python 3.13.4
v3.13.3: 3.13.3Compare Source
Python 3.13.3
v3.13.2: 3.13.2Compare Source
Python 3.13.2
v3.13.1: 3.13.1Compare Source
Python 3.13.1
v3.13.0: 3.13.0Compare Source
Python 3.13.0
Configuration
π Schedule: (UTC)
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.