build(deps-dev): bump semantic-release from 19.0.2 to 19.0.5

[dependabot]

Bumps semantic-release from 19.0.2 to 19.0.5.

Release notes

Sourced from semantic-release's releases.

v19.0.5

19.0.5 (2022-08-23)

Reverts

• Revert "fix(deps): update dependency yargs to v17" (#2534) (8f07522), closes #2534 #2533

v19.0.4

19.0.4 (2022-08-22)

Bug Fixes

• deps: update dependency yargs to v17 (#1912) (f419080)

v19.0.3

19.0.3 (2022-06-09)

Bug Fixes

• log-repo: use the original form of the repo url to remove the need to mask credentials (#2459) (58a226f), closes #2449

Commits

• 8f07522 Revert "fix(deps): update dependency yargs to v17" (#2534)
• 2f4bcef docs: add semantic-release-react-native to plugin list (#2523)
• f419080 fix(deps): update dependency yargs to v17 (#1912)
• 3bbf08c test(integration): upgrade the gitbox image to support arm architecture in ad...
• 846f4c2 build(deps): bump terser from 5.14.0 to 5.14.2 (#2513)
• bd294eb docs(plugin-list): add semantic-release-space plugin (#2502)
• c69445e docs: remove deprecated keyword in gitlab-ci.md (#2498)
• d80e2ea build(deps-dev): bump got from 11.8.3 to 11.8.5 (#2485)
• 9589a96 docs: fix typos (#2476)
• ec89bab docs: replace issue templates with forms (#2474)
• 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]
Once this PR has been reviewed and has the lgtm label, please assign belitre for approval by writing /assign @belitre in a comment. 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

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