Pushing to a branch while a workflow build have been queued on the same branch makes it fail

[AFCMS]

Contributing guidelines

• I've read the contributing guidelines and wholeheartedly agree

I've found a bug, and:

• The documentation does not mention anything about my problem
• There are no open or closed issues that are related to my problem

Description

I tend to push commits quickly to my branches. My github-builder based job requires some other jobs to finish first before starting, so I can expect 1-2mn between a push and the actual Docker job start.

This causes BuildKit to sometimes try to load the repository with a ref that do not match exactly the one triggering the job and fail with a checksum mismatch.

It's a pretty annoying limitation compared to the old actions/checkout based workflows which didn't have this problem.

Expected behaviour

The BuildKit Git source should not try to fetch a ref that isn't exactly the commit a job have been triggered on.

Actual behaviour

The BuildKit Git source used for the build specifies the branch ref, plus a checksum (commit hash of the push trigger).

At the time the Docker job starts, the branch may have been pushed another time, making the 'checksum' verification fail.

https://docs.docker.com/build/concepts/context/#url-queries

Repository URL

https://github.com/oktomusic/oktomusic

Workflow run URL

https://github.com/oktomusic/oktomusic/actions/runs/25625310677/job/75219376006

YAML workflow

https://github.com/oktomusic/oktomusic/blob/e3983a419bbb99b89e11b2e8310d8a60e50794c7/.github/workflows/ci.yml#L318-L374

Workflow logs

job-logs.txt

BuildKit logs

Additional info

No response

[crazy-max]

Yes this will be fixed in BuildKit v0.30.0 that will be released this week