[updatecli] update elastic stack version for testing 8.19.22-ada7f5f1-SNAPSHOT

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=8.19.22-ada7f5f1-SNAPSHOT": * dev-tools/integration/.env

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[github-actions]

TL;DR

Buildkite failed in both Package x86_64 and Package aarch64 due to an expired Debian Bullseye security apt metadata file during Docker image build, not because of this PR’s code change. Immediate action: retry once after mirror metadata refresh; if it persists, refresh the base image/repo configuration used by Dockerfile.build.

Remediation

• Retry the Buildkite run to confirm this is transient repository metadata staleness.
• If retry still fails, update the build environment to a current Debian base/repository set (or refresh apt source validity handling in the image path used by .buildkite/scripts/release_test.sh) before rerunning packaging.

Investigation details

Root Cause

docker build fails at Dockerfile.build line 5 on:

apt-get update && apt-get install --no-install-recommends -y zip && apt-get clean

The error in both architectures is:
E: Release file for (deb.debian.org/redacted) is expired ...
This indicates external apt repository metadata expiry in the build environment/image stream, not a failure introduced by the PR diff.

The PR only updates snapshot test version in dev-tools/integration/.env:

• dev-tools/integration/.env (single-line version bump)

That file is unrelated to the packaging Docker build step that failed.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16688
• Jobs/steps:
  • Package x86_64 (.buildkite/scripts/release_test.sh)
  • Package aarch64 (.buildkite/scripts/release_test.sh)
• Key log excerpts:
  • /tmp/gh-aw/buildkite-logs/fleet-server-package-x86_64.txt:
    • E: Release file for (deb.debian.org/redacted) is expired ...
    • ERROR: failed to solve: process "/bin/sh -c apt-get update ..." did not complete successfully: exit code: 100
  • /tmp/gh-aw/buildkite-logs/fleet-server-package-aarch64.txt:
    • same expired bullseye-security/InRelease error
    • same docker build failure at Dockerfile.build:5

Verification

• Not run locally; conclusion based on Buildkite logs and PR diff scope.

Follow-up

• If this repeats across new builds/PRs, track as CI infrastructure/package-source reliability issue (shared builder/base image) rather than PR-specific regression.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.