Skip to content

[Buildchain contract] kungfu-systems/libnode drift on v2 #80

Description

@github-actions

Buildchain consumer report

Summary

Buildchain floating runtime contract drift: breaking-drift

Consumer

Buildchain

  • Ref: v2
  • Version: sha256:3a82cbfd0cf15f85dac51b6ab03e3c3ce20ca2f3355d5319d969c43758ebb900
  • Failure code: buildchain-contract-breaking-drift
  • Fingerprint: 0e0604722ab4a37d71a49077c36f0717

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: v2
  • SHA: c92cf5d31c544dcde3dc7a11151a90e8a5f91d25
  • Contract digest: sha256:f289f70ad8c2b95a05f8309378da51ec5641c1ea7a145670137d096285b70dcd
  • Compatibility digest: sha256:36421b592a782decbfe31a7d8d42d70ce1100a56a2c4f4a0ccc21f0617dc72bf
  • Policy: major-compatible

Current Buildchain contract

  • Ref: v2
  • SHA: 6990341aaf93b51b936e5e66f380488d593daf6e
  • Contract digest: sha256:3a82cbfd0cf15f85dac51b6ab03e3c3ce20ca2f3355d5319d969c43758ebb900
  • Compatibility digest: sha256:407d6d5ee6a96a34d2cc30db9ac64cf4b1819ab6d77bd7a57a07a124f22101ca
  • Major line: v2

Compatibility

  • Status: breaking-drift
  • Compatible: no
  • surface breaking digest changed: buildchain-cli

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

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions