Skip to content

Update website for version 8.1.8#563

Merged
zuiderkwast merged 1 commit into
mainfrom
update-website-8.1.8
Jun 4, 2026
Merged

Update website for version 8.1.8#563
zuiderkwast merged 1 commit into
mainfrom
update-website-8.1.8

Conversation

@madolson
Copy link
Copy Markdown
Member

@madolson madolson commented Jun 2, 2026

This pull request updates the valkey website for the new release 8.1.8.

Changes:

  • Updated downloads page with new release information

This pull request is created automatically by the Valkey-Release-Automation

@madolson madolson requested a review from stockholmux as a code owner June 2, 2026 18:50
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 2, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds the release metadata document for Valkey 8.1.8 to the website repository. The new file includes version information, Docker Hub registry configuration with image tags, supported Linux distributions (jammy and noble) across two architectures (arm64 and x86_64), and a release header line.

Changes

Valkey 8.1.8 Release

Layer / File(s) Summary
Release metadata and distribution configuration
content/download/releases/v8-1-8.md
Release version header with title and date, extra metadata fields for artifact sourcing, Docker Hub container registry configuration with image identifiers and tags, package artifacts matrix with support for jammy and noble distributions across arm64 and x86_64 architectures, and the release description "Valkey 8.1.8 Release".

Possibly related PRs

  • valkey-io/valkey-io.github.io#555: Adds release metadata front-matter for Valkey 9.1.0 using the same artifact, container registry, and distribution/architecture structure.

Suggested reviewers

  • stockholmux
  • roshkhatri
  • murphyjacob4
  • lucasyonge

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Jun 2, 2026

Greptile Summary

Adds the download/release page for Valkey 8.1.8, generated automatically by the Valkey-Release-Automation tooling. The file is structurally identical to the previous patch releases.

  • Adds content/download/releases/v8-1-8.md with Docker Hub tags (8.1.8, 8.1.8-trixie, 8.1.8-alpine, 8.1.8-alpine3.21) and binary artifacts for jammy/noble on arm64/x86_64, matching the pattern of all recent releases.
  • The packages field is empty and the release body is a one-liner, consistent with the automation template used for prior 8.1.x releases.

Confidence Score: 5/5

Straightforward addition of a single auto-generated release page; no logic, no security surface, and the content matches the established pattern of prior patch releases.

The new file is a data-only Markdown page produced by the release automation. Its structure, date, Docker tags, and artifact list are all consistent with the immediately preceding release (v8-1-7). No template fields are missing or mismatched, and the change touches nothing that affects site behavior beyond rendering the new downloads entry.

No files require special attention.

Important Files Changed

Filename Overview
content/download/releases/v8-1-8.md New release page for Valkey 8.1.8, following the same structure as v8-1-7.md with correct date, Docker tags, and artifact metadata.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[v8-1-8.md added] --> B[Front-matter parsed by Zola/SSG]
    B --> C{Sections}
    C --> D[Docker Hub tags\n8.1.8 / 8.1.8-trixie\n8.1.8-alpine / 8.1.8-alpine3.23]
    C --> E[Binary artifacts\njammy: arm64 + x86_64\nnoble: arm64 + x86_64]
    C --> F[packages: empty]
    D --> G[Downloads page rendered]
    E --> G
    F --> G
Loading

Reviews (1): Last reviewed commit: "Updates downloads section for version 8...." | Re-trigger Greptile

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@content/download/releases/v8-1-8.md`:
- Around line 8-17: The container_registry entry for id "valkey/valkey" lists
tags ("8.1.8", "8.1.8-trixie", "8.1.8-alpine", "8.1.8-alpine3.23") that do not
exist on Docker Hub; query the Docker Hub repository for the actual published
tag names for valkey/valkey (using the web UI or API) and replace the tags array
under the container_registry block with the exact, published tag strings so the
site references real images.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8ce7cf2a-e601-4916-bbb4-e19124e545f8

📥 Commits

Reviewing files that changed from the base of the PR and between ed1d6f9 and 2b7add1.

📒 Files selected for processing (1)
  • content/download/releases/v8-1-8.md

Comment on lines +8 to +17
container_registry:
-
name: "Docker Hub"
link: https://hub.docker.com/r/valkey/valkey/
id: "valkey/valkey"
tags:
- "8.1.8"
- "8.1.8-trixie"
- "8.1.8-alpine"
- "8.1.8-alpine3.23"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify that all Docker Hub tags for this release are published.

echo "Checking Docker Hub tags for valkey/valkey..."

# Check each tag
for tag in "8.1.8" "8.1.8-trixie" "8.1.8-alpine" "8.1.8-alpine3.23"; do
  echo "Checking tag: $tag"
  # Query Docker Hub API for the specific tag
  response=$(curl -s "https://hub.docker.com/v2/repositories/valkey/valkey/tags/$tag")
  
  if echo "$response" | grep -q '"name"'; then
    echo "✓ Tag $tag exists"
  else
    echo "✗ Tag $tag NOT FOUND"
    echo "Response: $response"
  fi
  echo ""
done

Repository: valkey-io/valkey-io.github.io

Length of output: 911


🏁 Script executed:

#!/bin/bash
set -euo pipefail

base="https://hub.docker.com/v2/repositories/valkey/valkey/tags"

echo "Listing tags for valkey/valkey and searching for 8.1.8-related entries..."

page=1
page_size=100
found=0

while :; do
  url="${base}?page_size=${page_size}&page=${page}"
  echo "Fetching: $url"
  resp="$(curl -s "$url")"

  # If API returns empty or no results, stop
  if echo "$resp" | rg -q '"results":\[\]' || echo "$resp" | rg -q '"count":0'; then
    break
  fi

  matches="$(echo "$resp" | rg -o '"name":"[^"]+"' | cut -d'"' -f4 | rg '8\.1\.8')"
  if [ -n "${matches}" ]; then
    found=1
    echo "Found matching tags on page $page:"
    echo "$matches" | sort -u
  fi

  # stop if fewer than page_size results (likely last page)
  result_count="$(echo "$resp" | jq -r '.results | length' 2>/dev/null || echo 0)"
  if [ "$result_count" -lt "$page_size" ]; then
    break
  fi

  page=$((page+1))
  [ $page -gt 5 ] && break
done

if [ "$found" -eq 0 ]; then
  echo "No tags containing '8.1.8' found in the first few pages of the tag list."
fi

Repository: valkey-io/valkey-io.github.io

Length of output: 236


🏁 Script executed:

#!/bin/bash
set -u

base="https://hub.docker.com/v2/repositories/valkey/valkey/tags"
echo "Fetching tag list pages and searching for '8.1.8'..."

for page in 1 2 3; do
  url="${base}?page_size=100&page=${page}"
  tmp="/tmp/dockerhub_tags_${page}.json"

  http_code="$(curl -sS -o "$tmp" -w "%{http_code}" "$url" || true)"
  echo "Page $page HTTP $http_code"

  python3 - <<'PY'
import json, glob, os, re, sys
path=os.environ['TMP']
with open(path,'r',encoding='utf-8') as f:
    data=f.read()
try:
    j=json.loads(data)
except Exception as e:
    print("  Non-JSON response (first 300 chars):", data[:300].replace("\n"," "))
    sys.exit(0)

results=j.get('results',[]) or []
names=[r.get('name',"") for r in results]
matches=[n for n in names if re.search(r'8\.1\.8', n)]
print(f"  results_count={len(results)} matches={len(matches)}")
if matches:
    for n in sorted(set(matches)):
        print("   -", n)
PY
  done_tmp="/tmp/dockerhub_tags_${page}.json"
  TMP="$done_tmp" python3 - <<'PY2'
import json, os, re, sys
path=os.environ['TMP']
j=json.load(open(path,'r',encoding='utf-8'))
results=j.get('results',[]) or []
names=[r.get('name',"") for r in results]
matches=[n for n in names if re.search(r'8\.1\.8', n)]
print("  sample names (up to 10):", [n for n in names[:10]])
if not matches:
    print("  no '8.1.8' matches on this page")
else:
    for n in sorted(set(matches)):
        print("  match:", n)
PY2
done

Repository: valkey-io/valkey-io.github.io

Length of output: 1246


Fix Docker Hub tags for the 8.1.8 release (they don’t exist as written).

In content/download/releases/v8-1-8.md (container_registry valkey/valkey), Docker Hub returns 404 for tags 8.1.8, 8.1.8-trixie, 8.1.8-alpine, and 8.1.8-alpine3.23; update the configured tags to the ones actually published before the website update goes live.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/download/releases/v8-1-8.md` around lines 8 - 17, The
container_registry entry for id "valkey/valkey" lists tags ("8.1.8",
"8.1.8-trixie", "8.1.8-alpine", "8.1.8-alpine3.23") that do not exist on Docker
Hub; query the Docker Hub repository for the actual published tag names for
valkey/valkey (using the web UI or API) and replace the tags array under the
container_registry block with the exact, published tag strings so the site
references real images.

@zuiderkwast zuiderkwast merged commit c52e942 into main Jun 4, 2026
4 checks passed
@zuiderkwast zuiderkwast deleted the update-website-8.1.8 branch June 4, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants