Skip to content

Renovate cannot update the sha256 ref of remote sources #45

Description

@castrojo

Found during the CI/CD audit (#42).

renovate.json's custom regex manager updates the version variable in a BuildStream element (for example just_version in elements/lab-runner/just.bst), but it cannot update the sibling ref: sha256 that pins the downloaded artefact. Any such bump therefore produces a PR that either fails to fetch (hash mismatch) or, worse, is merged and breaks a build lane.

Until #42 there was no PR build to catch it, and non-major bumps were set to auto-merge.

Options to evaluate:

  • a Renovate postUpgradeTasks step running just bst source track <element> and committing the refreshed ref
  • a scheduled track-bst-sources workflow like projectbluefin/dakota has
  • dropping the sha256 pin for these sources (not preferred: it is the supply-chain guarantee)

Affects elements/lab-runner/{just,kubectl,argo}.bst.

Metadata

Metadata

Assignees

No one assigned

    Labels

    1-triageNew work awaiting human triage.3-clanker-queueWork admitted to the agent-maintained queue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions