The PATH variable is not preserved after setup
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 266
- Forks
- 110
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 3
Description
Describe the bug
The directories which are on the PATH environment variable are removed after the call to the setup-jfrog-cli action.
Current behavior
- name: Show PATH before
run: |
export PATH="/home/user/uv/:$PATH"
echo "path=$PATH" >>$GITHUB_ENV
env
- name: Setup JFrog CLI
uses: jfrog/setup-jfrog-cli@ff5cb544114ffc152db9cea1cd3d5978d5074946 # v4.5.11
env:
JF_URL: <URL>
JF_USER: <USER>
JF_PASSWORD: <PASS>
with:
disable-job-summary: true
disable-auto-build-publish: true
version: latest
- name: SHOW PATH AFter
run: |
env
Reproduction steps
No response
Expected behavior
No response
Setup JFrog CLI version
4.5.11
JFrog CLI version
2.75.1
Workflow operating system type and version
Ubuntu 22.04
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no source file or test; start by reproducing the Ubuntu 22.04 workflow around setup-jfrog-cli@v4.5.11 and inspect how the action updates PATH. Done means directories already present in PATH remain available after setup, with a regression check for the reported workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100