build(deps-dev): bump semantic-release from 17.4.3 to 18.0.1

[dependabot]

Bumps semantic-release from 17.4.3 to 18.0.1.

Release notes

Sourced from semantic-release's releases.

v18.0.1

18.0.1 (2021-11-24)

Bug Fixes

• bump @​semantic-release/commit-analyzer to 9.0.2 (#2258) (7f971f3)

v18.0.0

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

v18.0.0-beta.8

18.0.0-beta.8 (2021-09-17)

Bug Fixes

• plugins: upgraded to stable versions of the plugins (d5be46e)

v18.0.0-beta.7

18.0.0-beta.7 (2021-09-03)

Bug Fixes

• plugins: upgraded to the beta versions of the commit-analyzer and release-notes-generator plugins (d945374)

v18.0.0-beta.6

18.0.0-beta.6 (2021-09-03)

Bug Fixes

• npm: upgraded to the beta version of the npm plugin (#2103) (995469f)

v18.0.0-beta.5

18.0.0-beta.5 (2021-09-03)

Bug Fixes

• error: upgraded to the beta of the error plugin (10fb716)

v18.0.0-beta.4

... (truncated)

Commits

• 7f971f3 fix: bump @​semantic-release/commit-analyzer to 9.0.2 (#2258)
• e636621 docs(troubleshooting): typo (#2254)
• f2a2def docs(recipes): fix path to recipes (#2253)
• 628e29e chore(deps): update dependency got to v11.8.3 (#2251)
• 8fda7fd docs(recipes): moved recipes to sub-directories to align with gitbook expecta...
• 52d76a2 docs(plugin-list): updates semantic-release-plus/docker with updated lifecycl...
• f092dd1 chore(deps): update dependency nock to v13.2.1 (#2242)
• 03aa7d0 docs(badge): switched to proper semantic-release logo (#2235)
• bc146e4 docs(gitbook): updated the summary document so that missing pages are rendere...
• 5f9d1d1 chore(deps): update dependency nock to v13.2.0 (#2233)
• 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 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)

[ouzibot]

@dependabot[bot]: Invalid title for the PR, the title needs to be like:

• refactor: this is a refactor commit => if using semantic-release will trigger a patch release
• fix: this is a fix commit => if using semantic-release will trigger a patch release
• feat: this is a feature commit => if using semantic-release will trigger a minor release
• major: this is a major commit => if using semantic-release will trigger a major release
• doc: this is a doc commit => if using semantic-release won't trigger a new release
• build: this is a build commit => if using semantic-release will trigger a patch release
• no-release: this is a no-release commit => won't trigger a new release

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.

[ouzibot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
To complete the pull request process, please assign alexouzounis after the PR has been reviewed.
You can assign the PR to them by writing /assign @alexouzounis 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:

• OWNERS

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

[ouzibot]

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

I'm waiting for a ouzi-dev 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.

[dependabot]

Superseded by #152.