chore: bump actions/attest-build-provenance from 1.4.3 to 1.4.4 #1480
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
|
PyPI now bakes attestation in when using their action and trusted publishing (2.17.1 is our first example), so I'm thinking we probably don't need to do this ourselves any more. I'll do a bit more digging, but the better change may be to remove this step. |
Bumps [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance) from 1.4.3 to 1.4.4. - [Release notes](https://github.com/actions/attest-build-provenance/releases) - [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md) - [Commits](actions/attest-build-provenance@v1.4.3...v1.4.4) --- updated-dependencies: - dependency-name: actions/attest-build-provenance dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/github_actions/actions/attest-build-provenance-1.4.4
branch
from
6b97ef5 to
7e36d4b
Compare
If So for now, let's continue as-is, and we could look at (a) publishing the SLSA attestation to PyPI as well, and (b) consider dropping this when there's better client support for consuming. |
Bumps actions/attest-build-provenance from 1.4.3 to 1.4.4.
Release notes
Sourced from actions/attest-build-provenance's releases.
Commits
ef24412bump predicate from 1.1.3 to 1.1.4 (#310)36fa7d0bump@actions/attestfrom 1.4.2 to 1.5.0 (#309)390c0bbBump@types/nodefrom 22.8.1 to 22.8.7 in the npm-development group (#305)21da615Bump the npm-development group with 3 updates (#299)0704961Bump actions/publish-immutable-action in the actions-minor group (#298)d01b070Bump the npm-development group with 3 updates (#278)b1d65e4Add workflow file for publishing releases to immutable action package (#277)3a27694Bump@actions/corefrom 1.10.1 to 1.11.1 (#275)dff1ae6prevent e2e workflows on forks (#272)e5892d0Bump the npm-development group with 3 updates (#263)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)