Skip to content

Bump eve/pkg/pillar in all subprojects - #7039

Merged
rene merged 1 commit into
lf-edge:masterfrom
rene:bump-eve-pillar
Nov 5, 2026
Merged

rene merged 1 commit into
lf-edge:masterfrom
rene:bump-eve-pillar

Conversation

@rene

@rene rene commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Description

PR #5644 bumped eve-pillar on all subprojects while changing the pillar code, the hashes will not mach in the final master (merged) branch. This broke the SBOM generation and consequentially our publish workflow:

https://github.com/lf-edge/eve/actions/runs/41879234117

This PR just run make bump-eve-pillar to fix up all vendor code / go modules on all subprojects. It should fix the sbom generation and our publish workflow.

How to test and validate this PR

Regular tests are enough.

Changelog notes

None.

PR Backports

No backports, issue it's only in master.

Checklist

  • I've provided a proper description
  • I've added the proper documentation
  • I've tested my PR on amd64 device
  • I've tested my PR on arm64 device
  • I've written the test verification instructions
  • I've set the proper labels to this PR
  • I've checked the boxes above, or I've provided a good reason why I didn't
    check them.

This is also needed to fix SBOM generation, broken by commit 2cb4f79.

Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

evetest skip decision

This PR (make bump-eve-pillar run across subprojects) only touches go.mod/go.sum files in evetest/, pkg/installer/src/, pkg/recovertpm/src/, and pkg/vtpm/swtpm-vtpm/. It re-syncs vendored dependency hashes (notably github.com/lf-edge/eve/pkg/pillar, plus transitive bumps of go-containerregistry, logrus, go-logr, golang.org/x/{crypto,net,sys,text}, protobuf) so SBOM generation matches what was actually merged for #5644. There is no source code change anywhere in the diff — no pillar agent logic, no networking/storage/security/telemetry behavior changed.

Given that, every evetest suite is skipped as unrelated (Check A): none of them exercise "vendor hash / SBOM consistency," and the direct in-repo usages of the bumped libraries (logrus logging, x/sys/unix syscalls in the vtpm binary) are patch/minor-level bumps with no behavioral surface for e2e coverage to catch that compilation/build checks wouldn't already catch.

Skipped:

  • TestApplicationConnectivitySuite (and all its variants)
  • TestAppsSuite
  • TestBootstrapSuite
  • TestControllerFaultsSuite
  • TestDatastoreSuite
  • TestDeviceConnectivitySuite
  • TestDiagSuite
  • TestHardwareSuite
  • TestKonvertSuite
  • TestKubeRegistrationSuite
  • TestLPSSuite
  • TestNodeClusterResilienceSuite
  • TestNodeClusterSuite
  • TestPcibackErrorSuite
  • TestPortScanSuite
  • TestSecuritySuite (incl. all TestAppVTPM* variants)
  • TestStorageSuite
  • TestTelemetrySuite
  • TestUpgradeSuite
  • TestPVCUploadReport
  • TestVaultKeyKeptOnTPMError
  • TestKvmToKRepartitionAppVolume
  • TestKvmToKRepartitionVolmig

An engineer can comment /evetest all to force the full suite to run instead, or /evetest <name> <name> ... to run only specific tests/suites.

@rene
rene merged commit 7cea040 into lf-edge:master Nov 5, 2026
61 of 65 checks passed
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.

2 participants