🌱 Bump softprops/action-gh-release from 2.0.5 to 2.0.6

[dependabot]

Bumps softprops/action-gh-release from 2.0.5 to 2.0.6.

Release notes

Sourced from softprops/action-gh-release's releases.

v2.0.6

maintenance release with updated dependencies

Changelog

Sourced from softprops/action-gh-release's changelog.

2.0.6

• maintenance release with updated dependencies

2.0.5

• Factor in file names with spaces when upserting files #446 via @​MystiPanda
• Improvements to error handling #449 via @​till

2.0.4

• Minor follow up to #417. #425

2.0.3

• Declare make_latest as an input field in action.yml #419

2.0.2

• Revisit approach to #384 making unresolved pattern failures opt-in #417

2.0.1

• Add support for make_latest property #304 via @​samueljseay
• Fail run if files setting contains invalid patterns #384 via @​rpdelaney
• Add support for proxy env variables (don't use node-fetch) #386 via @​timor-raiman
• Suppress confusing warning when input_files is empty #389 via @​Drowze

2.0.0

• 2.0.0!? this release corrects a disjunction between git tag versions used in the marketplace and versions list this file. Previous versions should have really been 1.*. Going forward this should be better aligned.
• Upgrade action.yml declaration to node20 to address deprecations

0.1.15

• Upgrade to action.yml declaration to node16 to address deprecations
• Upgrade dependencies
• Add asset output as a JSON array containing information about the uploaded assets

0.1.14

• provides an new workflow input option generate_release_notes which when set to true will automatically generate release notes for you based on GitHub activity #179. Please see the GitHub docs for this feature for more information

0.1.13

• fix issue with multiple runs concatenating release bodies #145

0.1.12

• fix bug leading to empty strings subsituted for inputs users don't provide breaking api calls #144

... (truncated)

Commits

• a74c6b7 update changelog
• b909f76 update dist/index.js
• e49d08f chore(deps): bump glob from 8.0.3 to 10.4.2
• f12ad25 chore(deps): bump @​octokit/plugin-throttling from 4.3.2 to 9.3.0
• 7039a82 chore: release 2.0.6
• f9c2b6c chore: update deps and run build
• 73738a6 chore(deps): bump node dep and @types/node
• a500a35 Bump ts-jest from 29.0.3 to 29.1.4 (#459)
• 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 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)

[metal3-io-bot]

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

I'm waiting for a metal3-io 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 kubernetes/test-infra repository.

[tuminoid]

/ok-to-test
/override metal3-ubuntu-e2e-integration-test-release-1-7

[metal3-io-bot]

@tuminoid: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

• metal3-ubuntu-e2e-integration-test-release-1-7

Only the following failed contexts/checkruns were expected:

• metal3-centos-e2e-integration-test-release-1-7
• tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/ok-to-test
/override metal3-ubuntu-e2e-integration-test-release-1-7

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 kubernetes/test-infra repository.

[tuminoid]

/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tuminoid

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 [tuminoid]

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

[Rozzii]

/lgtm

[tuminoid]

/override metal3-centos-e2e-integration-test-release-1-7

[metal3-io-bot]

@tuminoid: Overrode contexts on behalf of tuminoid: metal3-centos-e2e-integration-test-release-1-7

In response to this:

/override metal3-centos-e2e-integration-test-release-1-7

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 kubernetes/test-infra repository.