build(deps-dev): bump semantic-release from 17.1.1 to 17.2.3

[dependabot]

Bumps semantic-release from 17.1.1 to 17.2.3.

Release notes

Sourced from semantic-release's releases.

v17.2.3

17.2.3 (2020-11-16)

Bug Fixes

• mask secrets when characters get uri encoded (ca90b34)

v17.2.2

17.2.2 (2020-10-29)

Bug Fixes

• don't parse port as part of the path in repository URLs (#1671) (77a75f0)
• use valid git credentials when multiple are provided (#1669) (2bf3771)

v17.2.1

17.2.1 (2020-10-12)

Reverts

• Revert "feat: throw an Error if package.json has duplicate "repository" key (#1656)" (3abcbaf), closes #1656 #1657

v17.2.0

17.2.0 (2020-10-11)

Features

• throw an Error if package.json has duplicate "repository" key (#1656) (b8fb35c)

v17.1.2

17.1.2 (2020-09-17)

Bug Fixes

• add logging for when ssh falls back to http (#1639) (b4c5d0a)

Commits

• c8d38b6 style: removed line breaks to align with xo rule (#1689)
• ca90b34 fix: mask secrets when characters get uri encoded
• 63fa143 docs(plugins): add listing for new plugin (#1686)
• 2bf3771 fix: use valid git credentials when multiple are provided (#1669)
• 77a75f0 fix: don't parse port as part of the path in repository URLs (#1671)
• d74ffef docs: add npm-deprecate-old-versions in plugins list (#1667)
• 3abcbaf Revert "feat: throw an Error if package.json has duplicate "repository" key (...
• b8fb35c feat: throw an Error if package.json has duplicate "repository" key (#1656)
• 18e35b2 docs: reorder default plugins list (#1650)
• e35e5bb docs(contributing): fix commit message examples (#1648)
• 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

You can disable automated security fix PRs for this repo from the Security Alerts page.

[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
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 #49.