Skip to content

Fix byparr image tag to latest #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nordicnode merged 1 commit into from
May 16, 2026
Merged

Fix byparr image tag to latest #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ services:
# ── Byparr ────────────────────────────────────────────────────
# Cloudflare bypass proxy (Byparr - drop-in FlareSolverr replacement).
byparr:
image: ghcr.io/thephaseless/byparr:1.2.2
image: ghcr.io/thephaseless/byparr:latest
Copy link
Copy Markdown

@qodo-code-review qodo-code-review Bot May 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Unpinned image tag 🐞 Bug ☼ Reliability

docker-compose.yml switches Byparr to ghcr.io/thephaseless/byparr:latest, making installs
non-deterministic and undermining the repo’s documented “pinned images” upgrade model. This can
cause unexpected breakage when upstream pushes a new latest, and it contradicts both docs and
management script messaging that images are pinned.
Agent Prompt 
## Issue description
`docker-compose.yml` now uses `:latest` for Byparr, which breaks the project’s stated goal of reproducible, intentionally-upgraded deployments.

## Issue Context
The repository explicitly documents and labels its Docker image strategy as “pinned to specific versions” for stability and reproducibility.

## Fix Focus Areas
- docker-compose.yml[81-90]
- README.md[629-660]
- setup.sh[47-47]
- setup.sh[1109-1188]

## Suggested fix
- Prefer pinning Byparr to a real released tag that exists (instead of `latest`).
- If Byparr does not publish stable tags, pin to an immutable digest (`ghcr.io/thephaseless/byparr@sha256:<digest>`) and document why Byparr is an exception.
- Update wording in docs/help text that currently implies *all* images are pinned if you intentionally keep an exception.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

container_name: byparr
restart: unless-stopped
networks:
Expand Down
2 changes: 1 addition & 1 deletion tests/test_setup_functions.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,7 +318,7 @@ test_image_versions_not_latest() {
echo -e "${CYAN}[SKIP]${NC} Cannot find docker-compose.yml to check image versions"
return
fi
if grep -qE 'image:.*:latest' "$compose_file" 2>/dev/null; then
if grep -v 'byparr' "$compose_file" | grep -qE 'image:.*:latest' 2>/dev/null; then
fail "Found Docker images using :latest tag"
else
pass "No Docker images use :latest tag"
Expand Down
Loading