fix(deps): update dependency probot to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
probot (source)	12.3.0 -> 13.3.10

---

Release Notes

probot/probot (probot)

v13.3.10

Compare Source

Bug Fixes

• deps: use fork of lru-cache to fix type issues (#​2104) (c87926b)

v13.3.9

Compare Source

Bug Fixes

• deps: bump @probot/pino to v2.5.0 (f26cf46), closes #​2102

v13.3.8

Compare Source

Bug Fixes

• deps: bump express to v4.21.0 (#​2085) (4c5310a)

v13.3.7

Compare Source

Bug Fixes

• types: avoid TS2590 errors in Context (#​2073) (23f6eab), closes #​1968

v13.3.6

Compare Source

Bug Fixes

• deps): Revert "fix(deps: update dependency lru-cache to v11" (#​2056) (60ff5b6), closes #​2049

v13.3.5

Compare Source

Bug Fixes

• remove eventsource dependency (#​2052) (caee841)

v13.3.4

Compare Source

Bug Fixes

• ci: Use organization-wide PROBOTBOT_NPM_TOKEN (#​2054) (cc86a53)

v13.3.0

Compare Source

Features

• set x-github-delivery header to event.id for all requests sent from context.octokit in event handlers (#​2027) (12944d5)

v13.2.2

Compare Source

Bug Fixes

• deps: update dependencies pino to v9, pino-http to v10 (#​2007) (ef7b9df)

v13.2.1

Compare Source

Bug Fixes

• probot: passes logger to webhooks (#​2011) (93007b6)

v13.2.0

Compare Source

Features

• security: Configure provenance (#​1997) (3f20320)

v13.1.2

Compare Source

Bug Fixes

• deps: update dependency express to v4.19.2 [security] (b1d3ac3)

v13.1.1

Compare Source

Bug Fixes

• deps: move bottleneck to dependencies (#​1992) (52de532)

v13.1.0

Compare Source

Features

• run: allow passing Octokit and log (#​1984) (d195264)

v13.0.2

Compare Source

Bug Fixes

• deps: update dependency commander to v12 (737835f)

v13.0.1

Compare Source

Bug Fixes

• deps: update dependency pino-http to v9 (#​1953) (5d95b73)

v13.0.0

Compare Source

Features

• v13 (#​1874) (948a1b7), closes #​1643
• Upgrade Octokit libraries to their latest major version

BREAKING CHANGES

• Drop support for NodeJS < 18
• replace node-fetch with the Fetch API
• default webhookPath is now /api/github/webhooks
• probot receive now only supports payloads in JSON format, previously also (unintionally) allowed JS.
• Probot now requires that payloads be passed as string to the .verify(), .verifyAndReceive() methods. Passing objects is no longer supported
• The middleware no longer accepts parsed payloads. You will have to pass it as a string

Note on Vercel deployments:

Set NODEJS_HELPERS environment variable to 0 in order to prevent Vercel from parsing the response body.
See Disable Helpers for detail.

v12.4.0

Compare Source

Features

• set x-github-delivery header to event.id for all requests sent from context.octokit in event handlers (#​2026) (f1985e5)

v12.3.4

Compare Source

Bug Fixes

• probot: passes logger to webhooks (#​2010) (3dcb058)

v12.3.3

Compare Source

Bug Fixes

• deps: @octokit/webhooks security update (#​1911) (02d81f8)

v12.3.2

Compare Source

Bug Fixes

• Fix async main function type (#​1672) (fc6886d)

v12.3.1

Compare Source

Bug Fixes

• typescript: simplify ProbotWebhooks object (#​1833) (7b09369)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @operate-first/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/probot
npm ERR!   probot@"13.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer probot@"^12.2.3" from @operate-first/[email protected]
npm ERR! node_modules/@operate-first/probot-kubernetes
npm ERR!   @operate-first/probot-kubernetes@"1.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/probot
npm ERR!   peer probot@"^12.2.3" from @operate-first/[email protected]
npm ERR!   node_modules/@operate-first/probot-kubernetes
npm ERR!     @operate-first/probot-kubernetes@"1.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-08T04_53_52_868Z-debug-0.log

[op1st-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign harshad16 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @operate-first/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/probot
npm ERR!   probot@"13.3.10" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer probot@"^12.2.3" from @operate-first/[email protected]
npm ERR! node_modules/@operate-first/probot-kubernetes
npm ERR!   @operate-first/probot-kubernetes@"1.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/probot
npm ERR!   peer probot@"^12.2.3" from @operate-first/[email protected]
npm ERR!   node_modules/@operate-first/probot-kubernetes
npm ERR!     @operate-first/probot-kubernetes@"1.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-06T23_31_34_539Z-debug-0.log