Skip to content

[Buildchain contract] kungfu-systems/libnode drift on v3-alpha #160

Description

@github-actions

Buildchain consumer report

Summary

Buildchain floating runtime contract drift: breaking-drift

Consumer

Buildchain

  • Ref: v3-alpha
  • Version: sha256:41501b9993621832a124f6ad5180e00b5b9b88435b70ad277cd842f1830aad2c
  • Failure code: buildchain-contract-breaking-drift
  • Fingerprint: 02615c8f218128ae3a02185c5a49d48d

Details

Buildchain contract drift

Summary

Buildchain detected breaking contract drift for a floating runtime ref before expensive Buildchain work continued.

Consumer

Accepted Buildchain contract

  • Ref: v3-alpha
  • SHA: c83cb444d79c2e647de6e12a0bfde68dfaf57701
  • Contract digest: sha256:a92b0189000ef05785d4c5097189e20856838adf94307c4174f36d5271616d16
  • Compatibility digest: sha256:008b1c5a90a787cf30106829ac7aca68ab501f6d9c375e415d9c5c6b89039f46
  • Policy: major-compatible

Current Buildchain contract

  • Ref: v3-alpha
  • SHA: 9d74fb4557e71992db3516b5ba750d57cb9f3521
  • Contract digest: sha256:41501b9993621832a124f6ad5180e00b5b9b88435b70ad277cd842f1830aad2c
  • Compatibility digest: sha256:32a651504c57829085dc8863f0e41dee98eb60708ff6dec958c9c7e4b1010102
  • Major line: v3

Compatibility

  • Status: breaking-drift
  • Compatible: no
  • surface breaking digest changed: auditable-demo

Suggested next action

Failing before heavy build is intentional. Review the Buildchain contract change, update the consumer workflow/configuration, or pin the previous Buildchain SHA.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions