Latest Results
Drop leftover pip --user settings from CI workflow (#13721)
<!-- Thank you for your contribution! -->
## What do these changes do?
Removes `PIP_USER: 1` (4×) and the
`PATH="${HOME}/Library/Python/3.11/bin:${HOME}/.local/bin:${PATH}"`
prefix left in the `autobahn` job. Both come from the time CI installed
deps with `pip install --user`. Since #12629 the `test` and `autobahn`
jobs use `astral-sh/setup-uv` with `activate-environment: true`, so
`.venv/bin` is already on `PATH` and uv ignores `PIP_USER`. The prefix
also put `~/.local/bin` in front of the venv. #10762 already removed the
same prefix from the `test` job.
Checked that nothing still depends on them. `PIP_USER` appears only in
`ci-cd.yml`. Nothing in `tests/`, `tools/` or the `Makefile` test
targets calls pip. The autobahn subprocesses run `sys.executable`. The
only `pip install` (`tests/autobahn/Dockerfile.aiohttp`) runs inside a
Docker build, which doesn't inherit the step env. In `cython-coverage`,
`PIP_USER` was only set on the pytest step, never on the install steps.
This is step 1 of #13718. The commit cherry-picks cleanly onto `3.15`
and `3.14` (checked locally), so please add `backport-3.14` +
`backport-3.15`. #13722 and #13723 bring the remaining master-only
workflow bits to those branches.
## Are there changes in behavior for the user?
No, CI-only.
## Is it a substantial burden for the maintainers to support this?
No. It removes 5 dead lines and makes the stable branches' workflows
easier to keep in sync.
## Related issue number
Part of #13718
## Checklist
- [x] I think the code is well written
- [ ] Unit tests for the changes exist — N/A, CI config; this PR's own
CI run exercises the edited jobs
- [ ] Documentation reflects the changes — N/A
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt` — N/A
- [x] Add a new news fragment into the `CHANGES/` folder
<details><summary>Local verification</summary>
```
$ git diff --shortstat upstream/master -- .github/workflows/ci-cd.yml
1 file changed, 5 deletions(-)
$ git grep -n -E 'PIP_USER|Library/Python' -- .github/workflows/
(no output)
$ python -c 'import yaml; d = yaml.safe_load(open(".github/workflows/ci-cd.yml")); print(len(d["jobs"]), "jobs")'
14 jobs
$ yamllint -f parsable -d '{extends: relaxed, rules: {line-length: disable}}' .github/workflows/ci-cd.yml | wc -l
29 # same as upstream/master
$ # trial cherry-pick in scratch worktrees
3.15: clean
3.14: clean
```
</details>
Drafted with Claude Opus 5 (Kōan); reviewed by: pending operator review.
---
### Quality Report
**Changes**: 3 files changed, 5 insertions(+), 5 deletions(-)
**Code scan**: clean
**Tests**: failed (FAILED)
**Branch hygiene**: clean
_Generated by [Kōan](https://koan.anantys.com)_ Drop leftover pip --user settings from CI workflow (#13721)
<!-- Thank you for your contribution! -->
## What do these changes do?
Removes `PIP_USER: 1` (4×) and the
`PATH="${HOME}/Library/Python/3.11/bin:${HOME}/.local/bin:${PATH}"`
prefix left in the `autobahn` job. Both come from the time CI installed
deps with `pip install --user`. Since #12629 the `test` and `autobahn`
jobs use `astral-sh/setup-uv` with `activate-environment: true`, so
`.venv/bin` is already on `PATH` and uv ignores `PIP_USER`. The prefix
also put `~/.local/bin` in front of the venv. #10762 already removed the
same prefix from the `test` job.
Checked that nothing still depends on them. `PIP_USER` appears only in
`ci-cd.yml`. Nothing in `tests/`, `tools/` or the `Makefile` test
targets calls pip. The autobahn subprocesses run `sys.executable`. The
only `pip install` (`tests/autobahn/Dockerfile.aiohttp`) runs inside a
Docker build, which doesn't inherit the step env. In `cython-coverage`,
`PIP_USER` was only set on the pytest step, never on the install steps.
This is step 1 of #13718. The commit cherry-picks cleanly onto `3.15`
and `3.14` (checked locally), so please add `backport-3.14` +
`backport-3.15`. #13722 and #13723 bring the remaining master-only
workflow bits to those branches.
## Are there changes in behavior for the user?
No, CI-only.
## Is it a substantial burden for the maintainers to support this?
No. It removes 5 dead lines and makes the stable branches' workflows
easier to keep in sync.
## Related issue number
Part of #13718
## Checklist
- [x] I think the code is well written
- [ ] Unit tests for the changes exist — N/A, CI config; this PR's own
CI run exercises the edited jobs
- [ ] Documentation reflects the changes — N/A
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt` — N/A
- [x] Add a new news fragment into the `CHANGES/` folder
<details><summary>Local verification</summary>
```
$ git diff --shortstat upstream/master -- .github/workflows/ci-cd.yml
1 file changed, 5 deletions(-)
$ git grep -n -E 'PIP_USER|Library/Python' -- .github/workflows/
(no output)
$ python -c 'import yaml; d = yaml.safe_load(open(".github/workflows/ci-cd.yml")); print(len(d["jobs"]), "jobs")'
14 jobs
$ yamllint -f parsable -d '{extends: relaxed, rules: {line-length: disable}}' .github/workflows/ci-cd.yml | wc -l
29 # same as upstream/master
$ # trial cherry-pick in scratch worktrees
3.15: clean
3.14: clean
```
</details>
Drafted with Claude Opus 5 (Kōan); reviewed by: pending operator review.
---
### Quality Report
**Changes**: 3 files changed, 5 insertions(+), 5 deletions(-)
**Code scan**: clean
**Tests**: failed (FAILED)
**Branch hygiene**: clean
_Generated by [Kōan](https://koan.anantys.com)_
(cherry picked from commit 1f2aadd234182ba9dd39fd54028d48772361b9f8)patchback/backports/3.14/1f2aadd234182ba9dd39fd54028d48772361b9f8/pr-13721 Latest Branches
0%
patchback/backports/3.14/6c0ed6f10f41d2820019041ae2359b1f26df6c6e/pr-13716 0%
aiolibsbot:koan/implement-13718-dependabot 0%
patchback/backports/3.14/1f2aadd234182ba9dd39fd54028d48772361b9f8/pr-13721 © 2026 CodSpeed Technology