relay: latest version by default, arm64-ready, build on AL2023 + OpenSSL 3#665
Open
tillkruss wants to merge 4 commits into
Open
relay: latest version by default, arm64-ready, build on AL2023 + OpenSSL 3#665tillkruss wants to merge 4 commits into
tillkruss wants to merge 4 commits into
Conversation
- Default RELAY_VERSION to empty; when unset, resolve the latest stable release from https://builds.r2.relay.so/meta/latest instead of pinning 0.9.1. - Download the Relay build matching the host architecture by deriving the suffix from `uname -m` (x86_64 -> x86-64, aarch64 stays aarch64). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2568dd7 to
d911b4f
Compare
…uild - Bump the base image to ":3" (Amazon Linux 2023 — glibc 2.34, OpenSSL 3) and enable the layer for PHP 8.2-8.5 in config.json (it was empty, so the layer was never built or published). - Switch from Relay's "centos7" build to its "el9" build, which links the system OpenSSL 3 / glibc already shipped by the AL2023 base image and the Bref runtime. - Drop the custom OpenSSL 1.1 compilation (and CA bundle). It existed only because the old centos7 build needed OpenSSL 1.1; the el9 build uses the system libssl.so.3 / libcrypto.so.3, which copy-dependencies bundles into the layer. This also removes the slowest step of the build. Verified locally with `make test layer=relay php_versions=85`: the extension loads on the bref/php-85 runtime, \Relay\Relay is available, and `php -v` is clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fc3e9e6 to
ca5a4fc
Compare
Relay is built for PHP 8.2-8.5, so relay-php-81 doesn't exist. Use the lowest built version (matching e.g. the Oracle oci8-php-83 row). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
szepeviktor
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modernizes and enables the Relay layer.
Changes
RELAY_VERSIONdefaults to empty and resolves the latest stable frombuilds.r2.relay.so/meta/latest(was pinned to0.9.1); still overridable via--build-arg RELAY_VERSION=x.y.z.uname -m(x86-64/aarch64) instead of hard-codingx86-64.:3, switched to Relay's self-containedel9relay-pkg.sobuild (links system OpenSSL 3 + glibc 2.34), removing the custom OpenSSL 1.1 compile — the slowest build step.config.jsonwas empty (so it was never built/published); now["82", "83", "84", "85"].Tested in Docker (PHP 8.3 & 8.5)
make test— extension loads,\Relay\Relayavailable, cleanphp -v.PING,SET/GET,INCRall round-trip.