CCR review: Azul Payara 6.37.0 for Jakarta EE Core Profile 10.0

[Copilot]

Review of the compatibility certification request for Azul Payara 6.37.0 against Jakarta EE Core Profile 10.0, following the CCR Review Guidance. This is a review-only task; no repository files were changed.

Verified

• TCK base URL — resolves on download.eclipse.org (HTTP 200).
• Dependent TCK SHA-256 (6/6) — Concurrency 3.0.2, CDI 4.0.13, Dependency Injection 2.0.2, JSON-B 3.0.0, JSON-P 2.1.1, RESTful WS 3.1.2 all match their official .zip.sha256 sidecars.
• Required standalone TCKs — All CORE_PROFILE-10 requirements present (CDI Lite covers Interceptors + Annotations signatures; DI, JSON-B, JSON-P, REST). Concurrency listed as extra.
• Attestations — EFTL and TCK-requirements checkboxes checked.

Findings for reviewer follow-up

• Core Profile TCK SHA-256 mismatch — CCR lists 7874244f…, but the published artifact (verified via .sha256 sidecar and by downloading + hashing the zip) is 702a84e3c6532fb0aad6a37443bf5e7fadbfb7cf0071271f3a1fdd10cab1229c. The CCR value matches all prior accepted Payara Core Profile CCRs (Compatibility certification request for Payara Server Enterprise 6.36.0 for Core Profile #1271, Compatibility certification request for Payara Server Enterprise 6.35.0 for Core Profile #1263, Compatibility certification request for Payara Server Enterprise 6.34.0 for Core Profile #1255) but not the actual file; the filer should confirm/correct the fingerprint.
• Unverifiable from sandbox — docs.payara.fish (TCK Results Summary), nexus.dev.payara.fish (product), and jakarta.ee (spec) are network-blocked here; a reviewer with access should confirm the results page loads login-free and reports no failures.

Recommendation

Dependent TCK hashes and required-TCK coverage are correct. Pending confirmation of the Core Profile TCK fingerprint and the TCK Results Summary page, the request is otherwise consistent with previously accepted Payara Core Profile CCRs.