Repository navigation
chore: bump APISIX-Runtime to 1.4.0 - #14041
Open
shreemaan-abhishek wants to merge 4 commits into
Open
shreemaan-abhishek wants to merge 4 commits into
shreemaan-abhishek wants to merge 4 commits into
Conversation
nic-6443
approved these changes
Oct 16, 2026
membphis
approved these changes
Oct 16, 2026
AlinsRan
approved these changes
Oct 16, 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.
Description
Bumps
APISIX_RUNTIMEfrom 1.3.19 to 1.4.0, with the version guard and the twoapisix-runtime-debugchecksums inci/linux-install-openresty.sh.What moves in apisix-runtime 1.4.0:
apisix_backend(keepalive declared beforebalancer_by_lua) andapisix_dubbo_backend(declared after) keep the 1.3.19 behavior.X25519MLKEM768to its default key shares, so TLS 1.3 handshakes offer it on both client and server sides.t/core/runtime-version.tasserts the runtime is at least nginx 1.31.1 and OpenSSL 3.5.9.Two fixes the new runtime needs:
process_metrics.luamirrors the head ofngx_cycle_tthrough FFI. nginx 1.29.7 appendsNGX_COMPAT_BEGIN(5)tongx_log_t, so in--with-compatbuilds such as apisix-runtime every field afternew_logmoves by 40 bytes. The plugin then read a garbageconnectionspointer, and its self check dereferenced it before comparing anything, which crashed every worker with SIGSEGV. The cdef now adds the spare slots on nginx 1.29.7+--with-compatbuilds, and the self check comparesconnection_nagainstworker_connectionsbefore it follows the pointer, so a future layout change disables the metric instead of crashing. Verified on runtimes 1.3.19 and 1.4.0: both now read 64 slots (60 free) with the event pointers matching.t/plugin/prometheus-process-metrics.tcovers it on 1.4.0.t/plugin/ocsp-stapling.t: OpenSSL 3.5s_clientprints the signature scheme name (ecdsa_secp256r1_sha256,rsa_pss_rsae_sha256) inPeer signature type, where 3.4 printedECDSA/RSA-PSS. TEST 17 and 20 now match either form.cc @nic-6443 for the prometheus change.
Checksums were taken from the published release artifacts:
Which issue(s) this PR fixes:
N/A
Checklist