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

[dependabot-preview]

Bumps semantic-release from 17.3.1 to 17.4.3.

Release notes

Sourced from semantic-release's releases.

v17.4.3

17.4.3 (2021-05-12)

Bug Fixes

• bump minimal version of lodash to address CVE-2021-23337 (#1931) (55194c1)

v17.4.2

17.4.2 (2021-03-11)

Bug Fixes

• deps: update dependency hosted-git-info to v4 (#1838) (44b3344)

v17.4.1

17.4.1 (2021-03-03)

Bug Fixes

• deps: peer dependecy error with marked-terminal (#1829) (07f12b9)

v17.4.0

17.4.0 (2021-02-26)

Features

• config: Use cosmiconfig defaults to support .cjs config files (#1815) (3ecc196), closes #1814

v17.3.9

17.3.9 (2021-02-12)

Bug Fixes

• update link to GitLab CI introduction (#1794) (a9be97b)

v17.3.8

17.3.8 (2021-02-08)

Bug Fixes

• deps: update dependency marked to v2 (a2eaed0)

v17.3.7

17.3.7 (2021-01-22)

... (truncated)

Commits

• 55194c1 fix: bump minimal version of lodash to address CVE-2021-23337 (#1931)
• e24ef71 docs(distribution-channels): fix branch name (#1925)
• 0435e35 docs(Plugin Developer Guide): More detailed lifecycle list and context descri...
• 1d1b52a chore(deps): update dependency p-retry to v4.5.0 (#1885)
• 72522c3 docs(Plugin Developer Guide): Update lifecycle list (#1874)
• 5489489 docs(github-actions): example suggests using ubuntu-latest (#1867)
• 1233717 docs: Add article to explain semantic release (#1856)
• 8fa4f9a chore(deps): lock file maintenance (#1861)
• f668935 chore(deps): update dependency got to v11.8.2 (#1858)
• 0f3c414 chore(deps): lock file maintenance (#1848)
• 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[ouzibot]

@dependabot-preview[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

Details

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-preview]

👋 If you need additional help with Dependabot, please fill out GitHub's Support form and your request will be routed to the right team at GitHub.

Be sure to include the details of any troubleshooting steps you've tried so far.

[ouzibot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot-preview[bot]
To complete the pull request process, please assign belitre after the PR has been reviewed.
You can assign the PR to them by writing /assign @belitre in a comment when ready.

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

Details

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-preview[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.

Details

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]

@dependabot-preview[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

Bumps semantic-release from 17.3.1 to 17.4.3.

Release notes

Sourced from semantic-release's releases.

v17.4.3

17.4.3 (2021-05-12)

Bug Fixes

• bump minimal version of lodash to address CVE-2021-23337 (#1931) (55194c1)

v17.4.2

17.4.2 (2021-03-11)

Bug Fixes

• deps: update dependency hosted-git-info to v4 (#1838) (44b3344)

v17.4.1

17.4.1 (2021-03-03)

Bug Fixes

• deps: peer dependecy error with marked-terminal (#1829) (07f12b9)

v17.4.0

17.4.0 (2021-02-26)

Features

• config: Use cosmiconfig defaults to support .cjs config files (#1815) (3ecc196), closes #1814

v17.3.9

17.3.9 (2021-02-12)

Bug Fixes

• update link to GitLab CI introduction (#1794) (a9be97b)

v17.3.8

17.3.8 (2021-02-08)

Bug Fixes

• deps: update dependency marked to v2 (a2eaed0)

v17.3.7

17.3.7 (2021-01-22)

... (truncated)

Commits

• 55194c1 fix: bump minimal version of lodash to address CVE-2021-23337 (#1931)
• e24ef71 docs(distribution-channels): fix branch name (#1925)
• 0435e35 docs(Plugin Developer Guide): More detailed lifecycle list and context descri...
• 1d1b52a chore(deps): update dependency p-retry to v4.5.0 (#1885)
• 72522c3 docs(Plugin Developer Guide): Update lifecycle list (#1874)
• 5489489 docs(github-actions): example suggests using ubuntu-latest (#1867)
• 1233717 docs: Add article to explain semantic release (#1856)
• 8fa4f9a chore(deps): lock file maintenance (#1861)
• f668935 chore(deps): update dependency got to v11.8.2 (#1858)
• 0f3c414 chore(deps): lock file maintenance (#1848)
• 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

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]

@dependabot-preview: PR needs rebase.

Details

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.