ci: Bump actions/attest-build-provenance from 4.1.1 to 4.2.2

[dependabot]

Bumps actions/attest-build-provenance from 4.1.1 to 4.2.2.

Release notes

Sourced from actions/attest-build-provenance's releases.

v4.2.2

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

• Bump actions/attest from 4.2.0 to 4.2.1 in the actions-minor group by @​dependabot[bot] in actions/attest-build-provenance#862

Full Changelog: actions/attest-build-provenance@v4.1.1...v4.2.2

Commits

• 4d10147 Bump actions/attest from 4.2.0 to 4.2.1 in the actions-minor group (#862)
• e3fe62e Bump the actions-minor group with 2 updates (#860)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Reefact]

Closing: the bump this proposes is on main as of #76 (50f0d4b), byte for byte — actions/attest-build-provenance@4d101475d8b20a2381f78447822ac1eab6504dd8 # v4.2.2. The SHA was checked against the GitHub API as the commit the v4.2.2 tag points at before it was carried over.

It was moved rather than merged because this pull request cannot pass the required SonarQube Cloud analysis check, for a reason unrelated to its content:

The format of the analysis property sonar.token= is invalid
##[error]Process completed with exit code 1.

GitHub serves Dependabot-triggered runs a separate dependabot secret scope, so secrets.SONAR_TOKEN arrives empty. .github/workflows/sonar.yml guards the case it anticipated —

# A pull request from a fork cannot read SONAR_TOKEN, so the analysis would fail for a reason
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository

— but a Dependabot branch lives in this repository, so head.repo.full_name == github.repository holds, the job runs, and it fails on the missing secret instead. The guard covers forks; it does not cover Dependabot.

That is structural rather than particular to this pull request: no Dependabot pull request can be merged while that check is required. Tracked as its own piece of work — the fix is not one line, since a skipped job reports no check at all and a required check that never reports blocks a merge just as a failing one does.

---

Generated by Claude Code

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.