GitHub
04/28/2025, 10:22 PM## v6.0.0 🌈 activate-environment and working-directory
## Changes
This version contains some breaking changes which have been gathering up for a while. Lets dive into them:
• Activate environment
• Working Directory
• Default `cache-dependency-glob`
• Use default cache dir on self hosted runners
### Activate environment
In previous versions using the inputautomatically activated a venv at the repository root. This led to some unwanted side-effects, was sometimes unexpected and not flexible enough.python-version
The venv activation is now explicitly controlled with the new input(false by default):activate-environment
- name: Install the latest version of uv and activate the environment
uses: astral-sh/setup-uv@v6
with:
activate-environment: true
- run: uv pip install pip
The venv gets created by the `uv venv` command so the python version is controlled by theinput or the filespython-version,pyproject.toml,uv.tomlin the.python-version.working-directory
### Working Directory
The new inputcontrols where we look forworking-directory,pyproject.tomlanduv.tomlfiles which are used to determine the version of uv and python to install..python-version
It can also be used to control where the venv gets created.
- name: Install uv based on the config files in the working-directory
uses: astral-sh/setup-uv@v6
with:
working-directory: my/subproject/dir
> [!CAUTION]
>
> The inputsandpyproject-filehave been removed.uv-file
### Defaultcache-dependency-glob
`@​ssbarnea` found out that the defaultwas not suitable for a lot of users.cache-dependency-glob
The old default... (truncated) Commits • `c7f87aa` bump to v6 in README (#382) • `aadfaf0` Change default cache-dependency-glob (#352) • `a0f9da6` No default UV_CACHE_DIR on selfhosted runners (#380) • `ec4c691` new inputs activate-environment and working-directory (#381) • `aa12905` chore: update known checksums for 0.6.16 (#378) • `fcaddda` chore: update known checksums for 0.6.15 (#377) • `fb3a0a9` log info on venv activation (#375) • See full diff in compare view [Dependabot compatibility score](https://camo.githubusercontent.com/a1d985e77a073ef91dc7070fc5fc15c7353f67eb680b016042ee84abcf29eca2/68747470733a2f2f646570656e6461626f742d6261646765732e6769746875626170702e636f6d2f6261646765732f636f6d7061746962696c6974795f73636f72653f646570656e64656e63792d6e616d653d61737472616c2d73682f73657475702d7576267061636b6167652d6d616e616765723d6769746875625f616374696f6e732670726576696f75732d76657273696f6e3d352e342e32266e65772d76657273696f6e3d362e302e30) 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 commands and options
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)
meltano/hubGitHub
04/28/2025, 10:32 PM