Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump sigstore/cosign-installer from 2.8.1 to 3.0.5 #8582

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 22, 2023

Bumps sigstore/cosign-installer from 2.8.1 to 3.0.5.

Release notes

Sourced from sigstore/cosign-installer's releases.

v3.0.5

What's Changed

Full Changelog: sigstore/cosign-installer@v3.0.4...v3.0.5

v3.0.4

v3.0.3

What's Changed

Full Changelog: sigstore/cosign-installer@v3.0.2...v3.0.3

v3.0.2

What's Changed

New Contributors

Full Changelog: sigstore/cosign-installer@v3...v3.0.2

v3.0.1

What's Changed

Full Changelog: sigstore/cosign-installer@v3.0.0...v3.0.1

v3.0.0

Breaking change

Cosign v2 has some breaking changes. Please check those: https://blog.sigstore.dev/cosign-2-0-released/

What's Changed

New Contributors

... (truncated)

Commits
  • dd6b2e2 download cosign releases from GitHub rather than GCS (#126)
  • 8e47e41 add --yes option to cosign sign (#125)
  • 87f4580 Remove warning about OIDC signing being experimental (#123)
  • 03d0fec Fix unsafe evaluation of inputs.use-sudo (#124)
  • 46b5db7 use intermediate environment variables to avoid risks of script injection (#122)
  • 84448ba we should rely upon the digests not the tags, typos (#121)
  • 204a51a bump to cosign v2.0.2 (#119)
  • 66dd3f3 Bump actions/checkout from 3.5.0 to 3.5.2 (#118)
  • 9e9de22 default cosign to v2.0.1 (#117)
  • 8348525 Bump actions/checkout from 3.4.0 to 3.5.0 (#116)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

Bumps [sigstore/cosign-installer](https://github.com/sigstore/cosign-installer) from 2.8.1 to 3.0.5.
- [Release notes](https://github.com/sigstore/cosign-installer/releases)
- [Commits](sigstore/cosign-installer@v2.8.1...v3.0.5)

---
updated-dependencies:
- dependency-name: sigstore/cosign-installer
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 22, 2023
@jenkins-x-bot
Copy link
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

@jenkins-x-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign babadofar
You can assign the PR to them by writing /assign @babadofar in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code needs-ok-to-test size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant