Skip to content

docs: document SBOM trimming for attestation size limit#810

Merged
gilescope merged 1 commit into
mainfrom
SRE-1910/sbom-attestation-docs
Feb 27, 2026
Merged

docs: document SBOM trimming for attestation size limit#810
gilescope merged 1 commit into
mainfrom
SRE-1910/sbom-attestation-docs

Conversation

@KrisF-Midnight

Copy link
Copy Markdown
Contributor

Overview

Documents the SBOM trimming strategy introduced in #809 to handle the 16MB actions/attest-sbom predicate size limit. Updates the image signing overview and operational runbook so operators know about the constraint and how to troubleshoot it.

🗹 TODO before merging

  • Ready

📌 Submission Checklist

  • Changes are backward-compatible (or flagged if breaking)
  • Pull request description explains why the change is needed
  • Self-reviewed the diff
  • I have included a change file, or skipped for this reason: docs-only change
  • If the changes introduce a new feature, I have bumped the node minor version
  • Update documentation (if relevant)
  • Updated AGENTS.md if build commands, architecture, or workflows changed
  • No new todos introduced

🧪 Testing Evidence

Docs-only change, no testing required.

  • Additional tests are provided (if possible)

🔱 Fork Strategy

  • Node Runtime Update
  • Node Client Update
  • Other:
  • N/A

Links

Document the 16MB actions/attest-sbom predicate limit and the
trimming strategy (strip relationships + minify JSON) in the
image signing overview and operational runbook.
@gilescope gilescope enabled auto-merge February 27, 2026 11:44
@gilescope gilescope added this pull request to the merge queue Feb 27, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Feb 27, 2026
@gilescope gilescope added this pull request to the merge queue Feb 27, 2026
Merged via the queue into main with commit 6c86db4 Feb 27, 2026
28 of 30 checks passed
@gilescope gilescope deleted the SRE-1910/sbom-attestation-docs branch February 27, 2026 20:57
gilescope pushed a commit that referenced this pull request Apr 8, 2026
changed:
- block range calculation no longer uses timestamps; it was prone to error if many slots were empty; now we get the blocks by querying SessionCommitteeManagement storage which consists epoch number
- `test_block_authors_match_committee_seats` is asserting whole list of authors instead of just one existence of committee in proper order

Refs: ETCM-9563
m2ux added a commit that referenced this pull request Apr 23, 2026
changed:
- block range calculation no longer uses timestamps; it was prone to error if many slots were empty; now we get the blocks by querying SessionCommitteeManagement storage which consists epoch number
- `test_block_authors_match_committee_seats` is asserting whole list of authors instead of just one existence of committee in proper order

Refs: ETCM-9563
Signed-off-by: Mike Clay <mike.clay@shielded.io>
m2ux added a commit that referenced this pull request Apr 23, 2026
changed:
- block range calculation no longer uses timestamps; it was prone to error if many slots were empty; now we get the blocks by querying SessionCommitteeManagement storage which consists epoch number
- `test_block_authors_match_committee_seats` is asserting whole list of authors instead of just one existence of committee in proper order

Refs: ETCM-9563
Signed-off-by: Mike Clay <mike.clay@shielded.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants