chore(deps): update dependency jfrog/jfrog-cli to v2.95.0

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
jfrog/jfrog-cli	minor	2.94.0 → 2.95.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

jfrog/jfrog-cli (jfrog/jfrog-cli)

v2.95.0: 2.95.0

Compare Source

What's Changed

Other Changes 📚

• Added logic for updating HF_ENDPOINT and HF_TOKEN from default or spe… by @​naveenku-jfrog in #​3379
• Added the huggingface command name by @​naveenku-jfrog in #​3383

Full Changelog: jfrog/jfrog-cli@v2.94.0...v2.95.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/jf:2.95.0

📦 Image Reference ghcr.io/uniget-org/tools/jf:2.95.0

digest	sha256:5e0653d443ac0a7bdc3aefe326648e030b11d2a7d27aaf02cd50665f654fc830
vulnerabilities
platform	linux/amd64
size	26 MB
packages	205

golang.org/x/net 0.50.0 (golang) pkg:golang/golang.org/x/net@0.50.0 Affected range >=0.50.0 <0.51.0 Fixed version 0.51.0 Description Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

github.com/docker/cli 29.0.3+incompatible (golang) pkg:golang/github.com/docker/cli@29.0.3+incompatible Uncontrolled Search Path Element Affected range >=19.03.0 <29.2.0 Fixed version 29.2.0 CVSS Score 7 CVSS Vector CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Description This issue affects Docker CLI through 29.1.5 Impact Docker CLI for Windows searches for plugin binaries in C:\ProgramData\Docker\cli-plugins, a directory that does not exist by default. A low-privileged attacker can create this directory and place malicious CLI plugin binaries (docker-compose.exe, docker-buildx.exe, etc.) that are executed when a victim user opens Docker Desktop or invokes Docker CLI plugin features, and allow privilege-escalation if the docker CLI is executed as a privileged user. This issue affects Docker CLI through v29.1.5 (fixed in v29.2.0). It impacts Windows binaries acting as a CLI plugin manager via the github.com/docker/cli/cli-plugins/manager package, which is consumed by downstream projects such as Docker Compose. Docker Compose became affected starting in v2.31.0, when it incorporated the relevant CLI plugin manager code (see docker/compose#12300), and is fixed in v5.1.0. This issue does not impact non-Windows binaries or projects that do not use the plugin manager code. Patches Fixed version starts with 29.2.0 This issue was fixed in docker/cli@1375933 (docker/cli#6713), which removed %PROGRAMDATA%\Docker\cli-plugins from the list of paths used for plugin-discovery on Windows. Workarounds None Resources Pull request: "cli-plugins/manager: remove legacy system-wide cli-plugin path" (cli-plugins/manager: remove legacy system-wide cli-plugin path docker/cli#6713) Patch: https://github.com/docker/cli/commit/13759330b1f7e7cb0d67047ea42c5482548ba7fa.patch Credits Nitesh Surana (niteshsurana.com) of Trend Research of TrendAI

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/22773653536.

[github-actions]

PR is unstable and cannot be merged. See https://github.com/uniget-org/tools/actions/runs/22773653536.