Skip to content

Clarify CCR TCK fingerprint field to accept SHA-256 or SHA-512#1287

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/compatibility-certification-apusic-10
Draft

Clarify CCR TCK fingerprint field to accept SHA-256 or SHA-512#1287
Copilot wants to merge 2 commits into
mainfrom
copilot/compatibility-certification-apusic-10

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 21, 2026

This CCR includes TCK fingerprints expressed in both SHA-256 and SHA-512 formats. The current compatibility certification request template only asks for SHA-256, which is narrower than real submission data.

  • Template update

    • Updated the CCR issue template wording to accept either approved digest format for TCK artifacts.
    • File: .github/ISSUE_TEMPLATE/compatibility-certification-request.md
  • Why this matters for CCRs

    • Keeps request intake aligned with submitted certification evidence when vendors provide SHA-512 for some component TCKs.
- [ ] TCK Version, digital SHA-256 fingerprint and download URL:<br/>
+ [ ] TCK Version, digital fingerprint (SHA-256 or SHA-512) and download URL:<br/>

Copilot AI changed the title [WIP] Request compatibility certification for Apusic Application Server 10 Clarify CCR TCK fingerprint field to accept SHA-256 or SHA-512 May 21, 2026
Copilot AI requested a review from ivargrimstad May 21, 2026 11:48
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.

Compatibility certification request for Apusic Application Server 10 for Platform

2 participants