Bump peter-evans/create-pull-request from 3.10.0 to 6.0.1

[dependabot]

Changes

Bumps peter-evans/create-pull-request from 3.10.0 to 6.0.1.

Release notes

Sourced from peter-evans/create-pull-request's releases.

Create Pull Request v6.0.1

⚙️ Fixes an issue where updating a pull request leads to the error Cannot read properties of undefined (reading 'number'). This was likely caused by GitHub fixing a long standing bug with an API endpoint, resulting in a breaking change.

What's Changed

• build(deps-dev): bump @​types/jest from 29.5.11 to 29.5.12 by @​dependabot in peter-evans/create-pull-request#2730
• build(deps-dev): bump prettier from 3.2.4 to 3.2.5 by @​dependabot in peter-evans/create-pull-request#2731
• build(deps-dev): bump @​types/node from 18.19.10 to 18.19.14 by @​dependabot in peter-evans/create-pull-request#2732
• build(deps): bump peter-evans/slash-command-dispatch from 3 to 4 by @​dependabot in peter-evans/create-pull-request#2748
• build(deps): bump peter-evans/create-pull-request from 5 to 6 by @​dependabot in peter-evans/create-pull-request#2747
• build(deps-dev): bump @​types/node from 18.19.14 to 18.19.15 by @​dependabot in peter-evans/create-pull-request#2759
• build(deps-dev): bump eslint-plugin-jest from 27.6.3 to 27.9.0 by @​dependabot in peter-evans/create-pull-request#2769
• build(deps-dev): bump @​types/node from 18.19.15 to 18.19.17 by @​dependabot in peter-evans/create-pull-request#2768
• build(deps-dev): bump @​types/node from 18.19.17 to 18.19.18 by @​dependabot in peter-evans/create-pull-request#2780
• build(deps-dev): bump eslint from 8.56.0 to 8.57.0 by @​dependabot in peter-evans/create-pull-request#2781
• fix: list pulls using the correct head format by @​peter-evans in peter-evans/create-pull-request#2792

Full Changelog: peter-evans/create-pull-request@v6.0.0...v6.0.1

Create Pull Request v6.0.0

Behaviour changes

• The default values for author and committer have changed. See "What's new" below for details. If you are overriding the default values you will not be affected by this change.
• On completion, the action now removes the temporary git remote configuration it adds when using push-to-fork. This should not affect you unless you were using the temporary configuration for some other purpose after the action completes.

What's new

• Updated runtime to Node.js 20
  • The action now requires a minimum version of v2.308.0 for the Actions runner. Update self-hosted runners to v2.308.0 or later to ensure compatibility.
• The default value for author has been changed to ${{ github.actor }} <${{ github.actor_id }}+${{ github.actor }}@users.noreply.github.com>. The change adds the ${{ github.actor_id }}+ prefix to the email address to align with GitHub's standard format for the author email address.
• The default value for committer has been changed to github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>. This is to align with the default GitHub Actions bot user account.
• Adds input git-token, the Personal Access Token (PAT) that the action will use for git operations. This input defaults to the value of token. Use this input if you would like the action to use a different token for git operations than the one used for the GitHub API.
• push-to-fork now supports pushing to sibling repositories in the same network.
• Previously, when using push-to-fork, the action did not remove temporary git remote configuration it adds during execution. This has been fixed and the configuration is now removed when the action completes.
• If the pull request body is truncated due to exceeding the maximum length, the action will now suffix the body with the message "...[Pull request body truncated]" to indicate that the body has been truncated.
• The action now uses --unshallow only when necessary, rather than as a default argument of git fetch. This should improve performance, particularly for large git repositories with extensive commit history.
• The action can now be executed on one GitHub server and create pull requests on a different GitHub server. Server products include GitHub hosted (github.com), GitHub Enterprise Server (GHES), and GitHub Enterprise Cloud (GHEC). For example, the action can be executed on GitHub hosted and create pull requests on a GHES or GHEC instance.

What's Changed

• Update distribution by @​actions-bot in peter-evans/create-pull-request#2086
• fix crazy-max/ghaction-import-gp parameters by @​fharper in peter-evans/create-pull-request#2177
• Update distribution by @​actions-bot in peter-evans/create-pull-request#2364
• Use checkout v4 by @​okuramasafumi in peter-evans/create-pull-request#2521
• Note about delete-branch by @​dezren39 in peter-evans/create-pull-request#2631
• 98 dependency updates by @​dependabot

New Contributors

• @​fharper made their first contribution in peter-evans/create-pull-request#2177
• @​okuramasafumi made their first contribution in peter-evans/create-pull-request#2521
• @​dezren39 made their first contribution in peter-evans/create-pull-request#2631

... (truncated)

Commits

• a4f52f8 fix: list pulls using the correct head format (#2792)
• 853c071 build(deps-dev): bump eslint from 8.56.0 to 8.57.0 (#2781)
• d2c126e build(deps-dev): bump @​types/node from 18.19.17 to 18.19.18 (#2780)
• 43d39c6 build(deps-dev): bump @​types/node from 18.19.15 to 18.19.17 (#2768)
• 5a9d206 build(deps-dev): bump eslint-plugin-jest from 27.6.3 to 27.9.0 (#2769)
• e0743ed build(deps-dev): bump @​types/node from 18.19.14 to 18.19.15 (#2759)
• e1529cb build(deps): bump peter-evans/create-pull-request from 5 to 6 (#2747)
• aad52e8 build(deps): bump peter-evans/slash-command-dispatch from 3 to 4 (#2748)
• a64ebdd build(deps-dev): bump @​types/node from 18.19.10 to 18.19.14 (#2732)
• 51b40af build(deps-dev): bump prettier from 3.2.4 to 3.2.5 (#2731)
• Additional commits viewable 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 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 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)

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

[HeavyWombat]

@SaschaSchwarze0 @qu1queee Not sure about this one. I would actually say we should switch from the digest to a version number in the PR job to be consistent with other usage. Also, since it is bumping the major version, we need to check https://github.com/peter-evans/create-pull-request/releases first. Thoughts?

[SaschaSchwarze0]

@SaschaSchwarze0 @qu1queee Not sure about this one. I would actually say we should switch from the digest to a version number in the PR job to be consistent with other usage. Also, since it is bumping the major version, we need to check https://github.com/peter-evans/create-pull-request/releases first. Thoughts?

Yeah, so, on this one I was not approving right away. Reason: all other actions (checkout, setup-go, setup-ko, etc) run as part of the PR actions. We therefore validated that they are still functional in the way we are using them with the new version. For this one, that is not the case. I assume it is used as part of the build strategy bump and/or the release logic where we PR an update to the readme to include the new tag. So yes, we need to be more careful in reading release notes.

[qu1queee]

@HeavyWombat can you pls do the enhancement, from the digest to the version in .github/workflows/release.yaml ?

[HeavyWombat]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[qu1queee]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qu1queee]

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

[dependabot]

A newer version of peter-evans/create-pull-request exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[HeavyWombat]

I needed to update the description for the release note linter to work, because it looks like the edit of the commits led to the author check in the Action to not register this as a Dependabot PR anymore.

[HeavyWombat]

@dependabot recreate

[dependabot]

Looks like peter-evans/create-pull-request is up-to-date now, so this is no longer needed.