Skip to content

ci: fix docker-check-build workflow - #633

Merged
fegmorte merged 1 commit into
mainfrom
fred/ci/fix-docker-scan
Jun 4, 2026
Merged

ci: fix docker-check-build workflow#633
fegmorte merged 1 commit into
mainfrom
fred/ci/fix-docker-scan

Conversation

@fegmorte

@fegmorte fegmorte commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Description of changes

Issue ticket number and link

PR Checklist

I attest that all checked items are satisfied. Any deviation is clearly justified above.

  • Title follows conventional commits (e.g. chore: ...).
  • Tests added for every new pub item and test coverage has not decreased.
  • Public APIs and non-obvious logic documented; unfinished work marked as TODO(#issue).
  • unwrap/expect/panic only in tests or for invariant bugs (documented if present).
  • No dependency version changes OR (if changed) only minimal required fixes.
  • No architectural protocol changes OR linked spec PR/issue provided.
  • No breaking deployment config changes OR devops label + infra notified + infra-team reviewer assigned.
  • No breaking gRPC / serialized data changes OR commit marked with ! and affected teams notified.
  • No modifications to existing versionized structs OR backward compatibility tests updated.
  • No critical business logic / crypto changes OR ≥2 reviewers assigned.
  • No new sensitive data fields added OR Zeroize + ZeroizeOnDrop implemented.
  • No new public storage data OR data is verifiable (signature / digest).
  • No unsafe; if unavoidable: minimal, justified, documented, and test/fuzz covered.
  • Strongly typed boundaries: typed inputs validated at the edge; no untyped values or errors cross modules.
  • Self-review completed.

Dependency Update Questionnaire (only if deps changed or added)

Answer in the Cargo.toml next to the dependency (or here if updating):

  1. Ownership changes or suspicious concentration?
  2. Low popularity?
  3. Unusual version jump?
  4. Lacking documentation?
  5. Missing CI?
  6. No security / disclosure policy?
  7. Significant size increase?

More details and explanations for the checklist and dependency updates can be found in CONTRIBUTING.md

@fegmorte
fegmorte requested a review from a team as a code owner June 4, 2026 14:01
@cla-bot cla-bot Bot added the cla-signed The CLA has been signed. label Jun 4, 2026
Comment thread .github/workflows/docker-check-build.yml Dismissed
Comment thread .github/workflows/docker-check-build.yml Dismissed
Comment thread .github/workflows/docker-check-build.yml Dismissed
Comment thread .github/workflows/docker-check-build.yml Dismissed
Comment thread .github/workflows/docker-check-build.yml Dismissed
@fegmorte
fegmorte merged commit 2178a6f into main Jun 4, 2026
81 checks passed
@fegmorte
fegmorte deleted the fred/ci/fix-docker-scan branch June 4, 2026 14:17
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

Consolidated Tests Results 2026-06-04 - 14:44:57

Test Results

passed 7 passed

Details

tests 7 tests
clock not captured
tool junit-to-ctrf
build build-and-test arrow-right test-reporter link #2565
pull-request ci: fix docker-check-build workflow link #633

test-reporter: Run #2565

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Pending ⏳ Other ❓ Flaky 🍂 Duration ⏱️
7 7 0 0 0 0 0 not captured

🎉 All tests passed!

Tests

View All Tests
Test Name Status Flaky Duration
k8s_test_crs_uniqueness 40.7s
k8s_test_insecure_keygen_encrypt_and_public_decrypt 2m 1s
k8s_test_insecure_keygen_encrypt_multiple_types 2m 9s
k8s_test_keygen_and_crs 2m 1s
k8s_test_keygen_uniqueness 4m 57s
k8s_test_centralized_insecure 56.0s
nightly_full_gen_tests_default_k8s_centralized_sequential_crs 1.7s

🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The CLA has been signed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants